Release prep v9.1.0 - #650
Merged
Merged
Conversation
|
GitHub Actions seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
added 2 commits
July 28, 2026 15:28
- Restore the accurate pre-existing changelog content (correct v9.0.0 entry with the 8.2.1 withdrawal note, no resurrected v8.2.1 section) and move it into HISTORY.md, which future release-prep runs don't touch. - Replace the auto-generated v9.1.0 section with an accurate one and add a note that this release raises the minimum puppetlabs/concat requirement to 7.4.0 (from #607), which can break dependency resolution for environments pinned to an older concat.
The release-prep automation had regenerated the whole tag history from scratch, dropping the v9.0.0 withdrawal note and inventing a bogus v8.2.1 section. Restore the full changelog to its accurate form (unchanged from v9.0.0 down) and prepend an accurate v9.1.0 entry with a note that this release raises the minimum puppetlabs/concat requirement to 7.4.0, which can break dependency resolution for environments pinned to an older concat. HISTORY.md already carries a duplicate copy of the v9.0.0-and-older content as the base the changelog is built from.
david22swan
reviewed
Jul 28, 2026
david22swan
reviewed
Jul 28, 2026
…in versioning rationale - HISTORY.md's top-level headers need to be bare version numbers (e.g. "## 9.0.0") for the changelog tooling to pick up from there going forward, not the markdown-link format used in CHANGELOG.md. - Also add the v9.1.0 entry to HISTORY.md so its note is protected from a future release-prep run the same way v9.0.0's is. - Note why this backwards-incompatible concat floor bump ships as a minor rather than a major: it follows too soon after v9.0.0, per the team's agreed exception for the first release after a major.
david22swan
approved these changes
Jul 28, 2026
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
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.
Automated release-prep through pdk-templates, corrected by hand.
The automation regenerates the entire tag history from scratch on every run, which dropped the v9.0.0 withdrawal note (explaining that 8.2.1 was mistakenly published as a patch despite dropping Puppet 7 support) and invented a bogus v8.2.1 section with no indication it was withdrawn.
Fixed:
Please verify before merging: