PHPackages alexandre-daubois/release-genius - 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. alexandre-daubois/release-genius ActiveLibrary[Utility & Helpers](/categories/utility) alexandre-daubois/release-genius ================================ Generate changelogs and tags from your git history 0.3.4(2y ago)53.4kMITPHPPHP >=8.2 Since Feb 10Pushed 2y ago1 watchersCompare [ Source](https://github.com/alexandre-daubois/release-genius)[ Packagist](https://packagist.org/packages/alexandre-daubois/release-genius)[ RSS](/packages/alexandre-daubois-release-genius/feed)WikiDiscussions main Synced 1mo ago READMEChangelog (3)Dependencies (7)Versions (10)Used By (0) Release Genius ============== [](#release-genius) [![PHPUnit](https://github.com/alexandre-daubois/release-genius/actions/workflows/php.yaml/badge.svg)](https://github.com/alexandre-daubois/release-genius/actions/workflows/php.yaml) [![Conventional version screenshot](asset/conv-vers.png)](asset/conv-vers.png) Requirements ------------ [](#requirements) - PHP 8.2 or higher - Git That's it! Why this package? ----------------- [](#why-this-package) This package is a simple tool to help you manage your changelog and versioning. It uses the [Conventional Commits](https://www.conventionalcommits.org/) standard to generate the changelog. This standard is widely used in the open-source community and is a great way to ensure that your commit messages are understandable and easy to parse. Unlike [this package](https://github.com/marcocesarato/php-conventional-changelog), this one is under **the MIT license**. This licence is more permissive than the GPL-3.0 licence. This can be a pain point for some projects, and it is the main motivation for creating Release Genius. Installation ------------ [](#installation) ``` composer require alexandre-daubois/release-genius ``` Usage ----- [](#usage) ### TL;DR [](#tldr) ``` # Initialize the package vendor/bin/release-genius --init # Upgrade to the next version (major, minor or patch) # CHANGELOG.md, package.json and composer.json will be updated vendor/bin/release-genius patch git push && git push --tags # Only update the changelog, composer.json and package.json vendor/bin/release-genius patch --no-commit ``` ### Available options [](#available-options) ``` Usage: ./release-genius [options] [--] [] Arguments: release type The type of release to be generated (major, minor, patch) Options: -f, --path=PATH The file to write the changelog to [default: "CHANGELOG.md"] -m, --mode=MODE The writing mode to use when writing the changelog to a file, between prepend, append and overwrite [default: "prepend"] -i, --init Initialize the changelog file and create a new git tag -r, --remote=REMOTE The remote to push the tag to; This is also used to generate URLs in the Changelog (use "none" if you don't use a remote) [default: "origin"] --remote-type=REMOTE-TYPE The type of remote to use; This is used to generate URLs in the Changelog ("github" or "gitlab") --skip-vendors Skip the update of package.json and composer.json --no-commit Do not create a commit and a tag, only update the changelog and vendor files if any ``` ### Initialize and upgrade the version [](#initialize-and-upgrade-the-version) The first time you use the package, you may need to initialize it. This is required when you don't have any tag in your repository and no changelog file exists. You can do this by running the following command: ``` vendor/bin/release-genius --init ``` This will create a new file called `CHANGELOG.md` in the root of your project. Also, it will create a new tag. You will be prompted to enter the version number you want to use. The version number should follow the [Semantic Versioning](https://semver.org/)specification. After the initialization, you can start using the package to manage your changelog and versioning. The package provides a few commands to help you with that. Imagine your current version is `1.0.0`. You can upgrade the version by running the following command: ``` # Upgrade the version to 1.0.1 vendor/bin/release-genius patch # Upgrade the version to 1.1.0 vendor/bin/release-genius minor # Upgrade the version to 2.0.0 vendor/bin/release-genius major ``` This will update the `CHANGELOG.md` file and create a new tag. The tag will **not**be pushed to the remote repository. This is something you need to do manually in order to ensure you're happy with the changes and the new version. #### Vendors JSON files [](#vendors-json-files) If a `package.json` file exists in the root of your project, the version number will be updated **in this file as well** (if present). The same goes for a `composer.json`file. #### Skip the commit and tag creation [](#skip-the-commit-and-tag-creation) If you want to create the tag and commit yourself to be extra careful, you can use the `--no-commit` option. Release Genius will only update the changelog and the vendor JSON files. ``` vendor/bin/release-genius minor --no-commit ``` ### Generate a changelog [](#generate-a-changelog) The changelog is generated thanks to your commit messages. All commits from the last tag to the current state of your repository will be used to generate it. You can customize the output path of the changelog file by using the `--path`option. By default, the changelog file is created in the root of your project and is called `CHANGELOG.md`. ``` vendor/bin/release-genius minor --path=docs/CHANGELOG.md ``` You can also choose the way to changelog file is generated. By default, the changelog file uses the `prepend` mode. This means that the new content is added at the beginning of the file. You can change this behavior by using the `--mode` option. The available modes are `append`, `prepend` and `overwrite`. ``` vendor/bin/release-genius minor --mode=append ``` ### Manage remotes [](#manage-remotes) This package will do its best to guess the remote repository URL. By default, it tries to find a remote called `origin`. If it fails, you can use the `--remote` option to specify the remote repository URL. ``` vendor/bin/release-genius minor --remote=upstream ``` This will allow to generate a changelog with the correct links to the commits and versions comparison. In case you don't use a guessable remote URL (because your hosting a private instance of Gitlab, for example), you can use the `--remote-type` option to specify the type of your remote repository. The available types are `github`, `gitlab`. ``` vendor/bin/release-genius minor --remote-type=gitlab ``` Specifying the type will help generate the good URL format, with your remote URL. The remote type **always** takes precedence over the automatic remote URL guessing. ### Health Score 29 — LowBetter than 60% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity25 Limited adoption so far Community7 Small or concentrated contributor base Maturity50 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 ~6 days Recently: every ~11 days Total 9 Last Release 773d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/4df244f8a69ff326bf04b0eafa163051f41826db1ffeb8ffa6b5b7fc425e6b9e?d=identicon)[alexandre-daubois](/maintainers/alexandre-daubois) --- Top Contributors [![alexandre-daubois](https://avatars.githubusercontent.com/u/2144837?v=4)](https://github.com/alexandre-daubois "alexandre-daubois (46 commits)") --- Tags semversemantichistorygittaggenerationversioncommitchangelogconventionreadmeconventional-changelogconventional-commit ### Code Quality TestsPHPUnit Static AnalysisPHPStan Code StylePHP CS Fixer Type Coverage Yes ### Embed Badge ![Health badge](/badges/alexandre-daubois-release-genius/health.svg) ``` [![Health](https://phpackages.com/badges/alexandre-daubois-release-genius/health.svg)](https://phpackages.com/packages/alexandre-daubois-release-genius) ``` ### Alternatives [marcocesarato/php-conventional-changelog Generate changelogs and release notes from a project's commit messages and metadata and automate versioning with semver.org and conventionalcommits.org 2511.3M109](/packages/marcocesarato-php-conventional-changelog)[shivas/versioning-bundle Symfony application versioning, simple console command to manage version (with providers e.g. git tag) of your application using Semantic Versioning 2.0.0 recommendations 1121.2M1](/packages/shivas-versioning-bundle)[nikolaposa/version Value Object that represents a SemVer-compliant version number. 1406.4M16](/packages/nikolaposa-version)[ramsey/conventional-commits A PHP library for creating and validating commit messages according to the Conventional Commits specification. Includes a CaptainHook action! 1931.2M122](/packages/ramsey-conventional-commits)[guanguans/ai-commit Automagically generate conventional git commit message with AI. - 使用 AI 自动生成约定式 git 提交信息。 39231.2k10](/packages/guanguans-ai-commit)[naneau/semver A decent, standards-compliant, Semantic Versioning (SemVer) parser and library 72496.2k13](/packages/naneau-semver) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)