Release playbook - php-tuf/composer-stager GitHub Wiki
- Before committing to a release...
- Check the issue queue for critical issues.
- Search the codebase for important
@todo
comments.
- Run automated tests with
composer all
.
- Make sure any needed documentation changes have been made--in the codebase and in the Wiki.
- Create a release tag. (See Branching & versioning.)
- Choose a semantic version number (
x.y.z
).
- Start the release with
git flow release start x.y.z
.
- If the release is a new major version (e.g.,
v1.0.0
), update the branch alias at composer.json:extra.branch-alias.dev-develop
accordingly.
- Finish the release with
git flow release finish x.y.z
.
- Push the release tag to GitHub along with the updated
develop
and main
branches.
- Create a GitHub release.
- Set the tag version and release title both to the new version number.
- Update the package at https://packagist.org/packages/php-tuf/composer-stager to publish the new release. Delete any extraneous versions it may create, e.g.,
dev-feature/example
.