Fix v1.6.61 release version and notes - #253
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release tagging after #252 failed because
composer.jsonstill declared1.6.60.RELEASE.mdalso retained the previous release's notes. Nov1.6.61tag was created.This updates the package version to
1.6.61and replaces the notes with the changes actually merged for this release: #251, release-branch CI, and #250. Onlycomposer.jsonandRELEASE.mdchange.Validation: Composer schema validation passed with existing constraint/version warnings; the local untracked lock file also reports drift and is not included. The version and release-notes headline agree on
v1.6.61, the notes have no template placeholder, andgit diff --checkpassed.After this PR merges and checks pass, run the Release Tag workflow (
release.yml) manually onmainwith version1.6.61. This is the workflow's supported recovery path and tags the corrected main HEAD. Do not rerun the original failed merge-event run: it checks out the original merge commit and would still see1.6.60.The manual dispatch creates the tag and triggers downstream release publication; merging this feature branch alone does not invoke automatic release tagging.