We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When running a development version of Terminus, the version should be reported as 1.1.1-dev (or similar)
1.1.1-dev
Terminus reports that it is version 1.1.1 for the stable version, and all dev versions after it, until the next stable tags.
Install a dev version of Terminus (e.g. git clone, or composer require pantheon-systems/terminus:*) and run terminus version
terminus version
This caused some confusion on #power-users, who thought that the 1.0.0 version was being re-tagged with new functionality.
The text was updated successfully, but these errors were encountered:
I think this is a good idea. I've been similarly bamboozled.
To implement this, we would need to
Do you concur @greg-1-anderson? If so, I'll implement.
Sorry, something went wrong.
Yes, that looks right.
Some form of version-string-manipulation-dance is what most projects do (remove -dev to tag a release, put it back when done).
No branches or pull requests
Expected behavior
When running a development version of Terminus, the version should be reported as
1.1.1-dev
(or similar)Actual behavior
Terminus reports that it is version 1.1.1 for the stable version, and all dev versions after it, until the next stable tags.
Steps to reproduce the behavior
Install a dev version of Terminus (e.g. git clone, or composer require pantheon-systems/terminus:*) and run
terminus version
This caused some confusion on #power-users, who thought that the 1.0.0 version was being re-tagged with new functionality.
The text was updated successfully, but these errors were encountered: