Download the PHP package fuzzyfox/composer-version without Composer
On this page you can find all versions of the php package fuzzyfox/composer-version. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package composer-version
composer-version
Bump a package version
Use it in a single project:
Or use it everywhere:
Synopsis
Description
Run this package in a directory to bump the version and write the new data back
to composer.json.
The newversion argument should be a valid composer version string,
or, one of the following:
major- Bump to the next major version.minor- Bump to the next minor version.patch- Bump to the next patch version.premajor [--preid=<prerelease-id>]- Bump to the next major version with a prerelease suffix.preminor [--preid=<prerelease-id>]- Bump to the next minor version with a prerelease suffix.prepatch [--preid=<prerelease-id>]- Bump to the next patch version with a prerelease suffix.devmajor- Bump to the next major version with a dev suffix.devminor- Bump to the next minor version with a dev suffix.devpatch- Bump to the next patch version with a dev suffix.prerelease [--preid=<prerelease-id>]- Bump the prerelease suffix number.from-git- Attempt to get the current version fromgit
If run in a git repo, it will also create a version commit and tag.
If pre-version, pre-version-commit, or post-version are in the composer
scripts property, they will
be executed as part of running composer version.
The exact order of execution is as follows:
- Check to make sure the git working directory is clean before getting started.
- Run the
pre-versionscript. These scripts have access to the oldversionincomposer.json. Any files you want added to the commit should be explicitly added usinggit add. - Bump
versionincomposer.jsonas requested. - Run the
pre-version-commitscript. These scripts have access to the newversionincomposer.json. Again, scripts should explicitly add generated files to the commit usinggit add. - Commit and tag.
- Run the
post-versionscript. Use it to clean up the file system or automatically push the commit and/or tag.
v1.0.0
This package will be considered v1.0.0 once it has full feature parity with
npm version (though some minor naming
tweaks for composer compat), and a full set of tests.
A possible additional feature that may be added as part of v1.0.0 will be the
ability to integrate w/ npm version to keep both composer.json and package.json
in sync for codebases that desire this.
License
This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/.
