release: promote main - #77
Merged
Merged
Conversation
Co-authored-by: Lewis Carhart <lewis@trycomp.ai> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
Everything on
mainthatreleasedoes not have yet. Merging this is what puts it infront of users, because
releaseis what a deploy and a plain clone both point at.Nothing releasable is waiting — no version bump will ride along with this.
Merge it with a merge commit, not a squash: a squash would give
releasea newcommit of its own, and the tags on
mainwould stop being ancestors of what you shipped.Summary by cubic
Run
release-pleaseonmainand clarify merge order so tags land on commits thatreleasereceives. Updates workflows and docs for the new flow and bumps to 1.2.0.release.ymlnow triggers on push tomainand targetsmain; adds summary note to merge the promotion PR after tagging.promote.ymlwarns if a pendingautorelease: pendingPR exists and to merge it first; reinforces using a merge commit, not a squash.pr-title.ymlskips conventional checks forrelease-please--*branches.CHANGELOG.md,package.json, and.release-please-manifest.jsonto 1.2.0.main, then promotion intorelease) and explainAUTOMATION_TOKENbehavior.Written for commit 39b93ff. Summary will update on new commits.