Prep work for 4.4.2 release - #279
Merged
Merged
Conversation
jonathannewman
force-pushed
the
maint/main/prep_4.4.2_release
branch
from
August 12, 2026 00:07
bbdfaad to
a12bb77
Compare
joshcooper
approved these changes
Aug 12, 2026
joshcooper
left a comment
joshcooper
left a comment
Contributor
There was a problem hiding this comment.
The unrelated changes are due to #247. If we care about preserving those, we should redo 247 and regenerate the changelog, but that's unrelated to this.
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
2 participants
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.
Standard release-prep, per
release-prep.sh(matches the pattern from #275):lib/beaker-puppet/version.rb:4.4.1→4.4.2.CHANGELOG.mdviagithub_changelog_generator.Picks up #278 ((PE-45697) ssl-first PuppetDB liveness check) and #277 (maint GitHubSig update) since the 4.4.1 tag.
Once this merges, someone still needs to manually tag and push
4.4.2to triggerrelease.yml(gem push to rubygems.org + GitHub Packages) — that step isn't automated by this PR.🤖 Generated with Claude Code
Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com