fix(ci): ship releases by opening a pull request into release - #114
Merged
Conversation
…ase` Updated the release workflow to ensure that all merges into the `release` branch are done via pull requests, adhering to the established ruleset. This change prevents direct pushes that could lead to untracked releases and ensures that the release process is streamlined and error-free. The workflow now automatically creates and merges a pull request from `main` to `release` when a new tag is created, improving the reliability of the deployment process.
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.
Opened automatically when
lewis/fk-claudewas pushed.The title is written from the diff and rewritten as you push, because this is squashed onto
mainand the title becomes the commit subject and the changelog line. Retitle it yourself and it is yours — the automation stops touching it.Summary by cubic
Ensure releases ship by creating and merging a PR from
mainintorelease, complying with the branch ruleset. This replaces direct merges that were blocked, so tags now reach production reliably..github/workflows/release.ymlto open and merge arelease: <tag>PR frommaintoreleaseviagh pr, with retries andworkflow_dispatchsupport.releaseis already up to date, reuses an existing open PR if present, and adds clear summary output for each path.CONTRIBUTING.mdto document the PR requirement forreleaseand clarify that deploys trackrelease.Written for commit f096f5a. Summary will update on new commits.