You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ampersarnie Should this have the same functionality as NPM-VERSION i.e | major | minor | patch | premajor | preminor | prepatch | prerelease | from-git] ?
I noticed npm version is only compatible with package.json files so couldn't even wrap this in it as it wouldn't work with PHP files.
Yeah they should, however, some of the naming between what was listed in the description and npm doesn't match word for word but are the same. i.e. premajor = major:beta
You can ignore the from-git version. To help with that comparison, here's what you can use:
NPM/semver
Build Tools
Example Result (x|y)
major
major
x.0.0
minor
minor
1.x.0
patch
patch
1.0.x
premajor
major:beta
x.0.0-beta.y
preminor
minor:beta
1.x.0-beta.y
prepatch
patch:beta
1.0.x-beta.y
If you're unsure on what these versions mean, take a look at our internal RFC on Semantic Versioning.
Having a command that allows for incrementing the version of a specific plugin would help with how we define and perform semver increments.
Example Command Usage
Patch
build-tools version patch # 1.2.2 → 1.2.3
Minor
build-tools version minor # 1.2.3 → 1.3.0
Major
build-tools version major # 1.3.0 → 2.0.0
Beta
Increment Multiple
The text was updated successfully, but these errors were encountered: