Repository navigation
Allow manual releases without pending changelog changes - #44
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.
The manual 1.1.0 release failed in
tools/release.php preparebecause 1.0.9 had already frozen both changelogs and no pending sections remained.Allow an unused selected version without pending entries by adding matching maintenance notes to both changelogs. Preserve historical entries verbatim and retain rejection of duplicate, malformed or one-sided pending metadata before any writes. Add regression coverage and document the behavior.
Validation on commit
3bb07f1cc4b1c7ae5e77124cce08ce7a4d3ab68f: all seven checks passed, including PHP contracts on 8.3/8.4, installed Joomla on all four PHP/database combinations, and the installed JCB golden image. The contracts workflow includes the expanded release metadata tests.Recovery: after merging, start a new component Release workflow on main with
1.1.0. A rerun of the old failed job uses the old helper. The existing immutablev1.0.9tag is preserved. Its deleted run cannot be inspected; available Git history shows it reached component feed publication, but the feed has no checksum and the package has no v1.0.9 tag, so publication did not complete. Wait for both the component release and package update workflow to succeed before declaring the release published.