Download the PHP package naneau/project-versioner without Composer
On this page you can find all versions of the php package naneau/project-versioner. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download naneau/project-versioner
More information about naneau/project-versioner
Files in naneau/project-versioner
Package project-versioner
Short Description A tool to maintain project/sub-project versions based on Composer, file mtimes, etc.
License MIT
Informations about the package project-versioner
PHP Project Versioner
This is a simple tool to obtain "versions" for projects in PHP.
Installation
Installation through composer:
Examples
This library is based around a "Versioner", which accepts one or more "Readers".
Using Git
If your project is maintained using Git, you can look at it for versions.
Commit
Use the last commit as a version:
Tag
Use the latest tag (reachable from this commit):
Described Version
Use the output of git describe
, which combines the latest (reachable) tag and subsequent commits:
Using Files
Reading Version From A Single File
Imagine you maintain a file called VERSION
that you (or your CI stack) fills with a version.
Using MTime
In a common scenario, a set of files is (independently) updated, and you want to use the highest/most recent time (mtime
) as a version. This version can be used to bust caches, etc.:
Using Contents
Using a different reader it is possible to use the contents of the files found:
Composer
If your project depends on a set of Composer dependencies, you can use the Composer readers to obtain a version based on installed packages.
All Packages
To look at all packages combined:
Using A Specific Package
Or, looking for a specific package:
Combining Readers
For some projects you may want to combine readers, for instance as a fallback mechanism if one reader does not provide output, or to get a version composed of more than one reader's output.
Combining Composer and Git:
Notes
- Obtaining a version inevitably uses (potentially expensive) I/O. You may want to cache the results.
- The
exec
based Git readers are UN*X only for now