Skip to content

RELEASE.md

Latest commit

 

History

History
18 lines (15 loc) · 937 Bytes

RELEASE.md

File metadata and controls

18 lines (15 loc) · 937 Bytes
Raw

Release process

  1. Update CHANGELOG.md: move entries from [Unreleased] to a new [X.Y.Z] - YYYY-MM-DD section. (This project does not store version in composer.json; Packagist uses the git tag.)
  2. Update UPGRADING.md if the release has upgrade notes.
  3. Run pre-release checks: make release-check (cs-fix, cs-check, rector-dry, phpstan, test-coverage, and demo release-check).
  4. Commit all changes, create an annotated tag (e.g. v1.0.0), and push branch and tag. The release workflow creates the GitHub Release from the changelog.
  5. Confirm Packagist auto-update (or trigger manual sync).

Example for v1.0.0

git add docs/CHANGELOG.md docs/UPGRADING.md docs/RELEASE.md README.md
git status   # review
git commit -m "Release v1.0.0: initial Console Debug Bundle"
git tag -a v1.0.0 -m "Release v1.0.0: initial Console Debug Bundle"
git push origin main
git push origin v1.0.0