Skip to content

RELEASE.md

Latest commit

 

History

History
18 lines (15 loc) · 912 Bytes

RELEASE.md

File metadata and controls

18 lines (15 loc) · 912 Bytes

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 optionally demo healthchecks).
  4. Commit all changes, create an annotated tag (e.g. v1.2.3), and push branch and tag. The release workflow will create the GitHub Release with the changelog.
  5. Publish the package to Packagist if applicable (usually automatic when the tag is pushed).

Example for v1.2.3

git add -A
git status   # review
git commit -m "Release 1.2.3: Twig override order, demo Composer path, docs"
git tag -a v1.2.3 -m "Release 1.2.3"
git push origin main
git push origin v1.2.3