PHPackages bonndan/release-manager - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. bonndan/release-manager ActiveLibrary[Utility & Helpers](/categories/utility) bonndan/release-manager ======================= Release Manager for semantic version releases of composer packages and projects. 0.5.6(12y ago)2620.2k↓56.5%[4 issues](https://github.com/bonndan/release-manager/issues)MITPHPPHP >=5.3.3 Since Aug 25Pushed 2y ago6 watchersCompare [ Source](https://github.com/bonndan/release-manager)[ Packagist](https://packagist.org/packages/bonndan/release-manager)[ Docs](http://github.com/bonndan/release-manager)[ RSS](/packages/bonndan-release-manager/feed)WikiDiscussions master Synced 2d ago READMEChangelogDependencies (2)Versions (19)Used By (0) Release with the flow. ====================== [](#release-with-the-flow) [![Build Status](https://camo.githubusercontent.com/065978269e10d2ce604c52444fb29243fcd16c989e3307cf8d41c87c0d251120/68747470733a2f2f7365637572652e7472617669732d63692e6f72672f626f6e6e64616e2f72656c656173652d6d616e616765722e706e673f6272616e63683d6d6173746572)](https://travis-ci.org/bonndan/release-manager) Release Manager is a PHP command line tool to help you keeping track of release versions. - It uses your composer file to store and retrieve information. - It enforces \[semantic versions\] (). - Works closely together with [git flow](http://nvie.com/posts/a-successful-git-branching-model/). [![screenshot](https://github.com/bonndan/release-manager/raw/develop/docs/screen-flow.png "Using git flow")](https://github.com/bonndan/release-manager/raw/develop/docs/screen-flow.png) This is a fork of Liip's Relase Management Tool [RMT](https://github.com/liip/RMT). Kudos to the original authors for this tool. Use with git-flow ----------------- [](#use-with-git-flow) ``` ./RMT release ./RMT finish ``` or to hotfix (patch-bump version based on master branch) ``` ./RMT hotfix ./RMT finish ``` Installation ------------ [](#installation) In order to use RMT your project should use [Composer](http://getcomposer.org/) as RMT will be installed as a dev-dependency. Just go on your project root directory and execute: ``` php composer.phar require --dev bonndan/release-manager 0.5.* # lastest stable # or php composer.phar require --dev bonndan/release-manager dev-develop # lastest unstable ``` Then you must initialize RMT by running the following command: ``` php vendor/bonndan/release-manager/command.php init ``` This command will create for you a `extra/rmt` section in your composer.json. You should adapt the configuration to your needs. A good example is the \[composer file of this project\] (). From that point on you can start using it, just execute it: ``` ./RMT ``` Usage with manual workflow -------------------------- [](#usage-with-manual-workflow) Using RMT is very straightforward, you just have to run the command: ``` ./RMT release ``` RMT will then do the following tasks: - Execute the prerequisites checks - Ask the user to answers potentials questions - Generate a new version number - Execute the pre-release actions - Persist the new version number - Execute the post-release actions [![screenshot](https://github.com/bonndan/release-manager/raw/master/docs/screen.png "In-Dev Screenshot")](https://github.com/bonndan/release-manager/raw/master/docs/screen.png) ### Additional commands [](#additional-commands) The `release` command is the main behavior of the tool, but some extra commands are available: - `current` will show your project current version number - `changes` will show the last which would be part of the next release - `init` create a config section in your composer.json file Configuration ------------- [](#configuration) All RMT configuration have to be done in the `composer.json`. You can optionally define a list of actions that will be executed and before or after the release of a new version and where you want to store the version (in a changelog file, as a VCS tag, etc…). The file is divided in 5 root elements: - `vcs`: The type of VCS you are using, can be `git`, `svn` or `none` - `prerequisites`: A list `[]` of prerequisites that must be matched before starting the release process - `preReleaseActions`: A list `[]` of actions that will be executed before the release process - `versionPersister`: The persister to use to store the versions - `postReleaseActions`: A list `[]` of actions that will be executed after the release All the entries of this config are working the same way: You have to specify the class you want to handle the action or provide an abbrevation for classes provided by Release Manager.: ### Semantic Version Generator [](#semantic-version-generator) Release Manager only allows semantic versions without prefixes. See (Semantic versioning)\[\]. The release version can be increased by: - major - minor - patch - build number ### Version persister [](#version-persister) Class is charged of saving/retrieving the version number - composer: uses the version from the composer file (default and recommended) - vcs-tag: Save the version as a VCS tag - changelog: Save the version in the changelog file ### Prerequisite actions [](#prerequisite-actions) Prerequisite actions are executed before the interactive part. - working-copy-check: Check that you don't have any VCS local changes before release - display-last-changes: display your last changes before release ### Actions [](#actions) Actions can be used for pre or post release parts. - execute: Execute any script via system() call. Return values greather than zero cause exceptions to be thrown. - changelog-update: Update a changelog file - vcs-commit: Process a VCS commit - vcs-tag: Tag the last commit - vcs-publish: Publish the changes (commit and tags) - composer-update: Update the version number in a composer file Configuration examples ---------------------- [](#configuration-examples) Most of the time, it will be easier for you to pick up and example bellow and to adapt it to your needs. ### The configuration for Release Manager explained [](#the-configuration-for-release-manager-explained) ``` { "rmt": { "vcs": "git", "prerequisites": [ "working-copy-check", "display-last-changes" ], "preReleaseActions": [ { "name": "execute", "script": "phpunit test" }, { "name": "version-stamp", "const": "RMT_VERSION" }, { "name": "changelog-update" }, { "name": "changelog-render" } ], "postReleaseActions": [ "vcs-commit" ] } } ``` - Git is the version control system - Before releasing it is checked that the working copy is clean and the last changes are displayed. - The version stamp (autogenerated php file) and the changelog are updated with the new version. - PHPUnit (generic call) is executed and stops releasing if it fails. - Not configured here: The composer version persister updates the composer.json file. - After the release all changes are committed. ### Pushing automatically [](#pushing-automatically) ``` { /* ... */ "postReleaseActions": [ "vcs-commit", "vcs-publish" ], } ``` ### No VCS, changelog updater only [](#no-vcs-changelog-updater-only) ``` { "versionPersister": "changelog" } ``` Contributing ------------ [](#contributing) If you would like to help, to submit one of your action script or just to report a bug: just go on the project page: Requirements ------------ [](#requirements) PHP 5.3 Composer Authors ------- [](#authors) - Laurent Prodon Liip AG - David Jeanmonod Liip AG - Daniel Pozzi License ------- [](#license) RMT is licensed under the MIT License - see the LICENSE file for details ### Health Score 33 — LowBetter than 72% of packages Maintenance17 Infrequent updates — may be unmaintained Popularity34 Limited adoption so far Community9 Small or concentrated contributor base Maturity57 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~15 days Total 15 Last Release 4487d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/143695?v=4)[bonndan](/maintainers/bonndan)[@bonndan](https://github.com/bonndan) --- Top Contributors [![bonndan](https://avatars.githubusercontent.com/u/143695?v=4)](https://github.com/bonndan "bonndan (287 commits)") --- Tags releaseversionsemantic versioningvcs tag ### Embed Badge ![Health badge](/badges/bonndan-release-manager/health.svg) ``` [![Health](https://phpackages.com/badges/bonndan-release-manager/health.svg)](https://phpackages.com/packages/bonndan-release-manager) ``` ### Alternatives [liip/rmt Release Management Tool: a handy tool to help releasing new version of your software 461462.8k78](/packages/liip-rmt)[friendsoftypo3/content-blocks TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML 103519.9k53](/packages/friendsoftypo3-content-blocks)[phel-lang/phel-lang Phel is a functional programming language that compiles to PHP 5186.0k18](/packages/phel-lang-phel-lang)[dagger/dagger Dagger PHP SDK 261.1k](/packages/dagger-dagger) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)