Repository navigation
chore(ci): merge release PRs weekly instead of immediately - #61
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
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.
Until now,
release-please.ymlturned on auto-merge for every release PR as soon as it was opened. Sincemainhas no required checks, the PR merged within seconds, so every feature merge became its own release (see #34–#36, #41–#43, #56, #59).This switches to the setup used in
udondan/cfn-teleport:release-please.yml: removes the auto-merge step. release-please now only opens and updates the release PR. The draft release andpublishchain are unchanged.release-automerge-weekly.yml: runs Sundays at 18:00 UTC (or viaworkflow_dispatch). It finds the openrelease-please--branches--mainPR, stops with an error if its checks aren't passing, and otherwise squash-merges it withOVERRIDE_TOKEN. The PAT is what makes the merge trigger the release-please run that creates and publishes the release. The job uses theghCLI instead of cfn-teleport's unpinnedjuliangruber/*actions.CLAUDE.md: documents the weekly merge.