chore: add release branch workflows#4738
Merged
lukaisailovic merged 14 commits intomainfrom Jul 30, 2025
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
10 Skipped Deployments
|
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Contributor
Coverage Report
File CoverageNo changed files found. |
github-actions
bot
force-pushed
the
chore/release-branch
branch
from
98ac485 to
6407ad8
Compare
0xmkh
approved these changes
Jul 30, 2025
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
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
3 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.
Description
Introduce a new release workflow with the release branch.
Added a manual workflow to start a release which will automatically figure out the next version and create a release branch. It will also start a Slack workflow to notify everyone involved.
Once we create a branch with
release/xyzpattern, prepare release job will be ran to create a Publish PR.On commits to release branch, we either update the Publish PR or if we detect version bump we trigger the release.
If the release is triggered, we PR back to main to merge the version bump and changeset removal.
Type of change
Associated Issues
For Linear issues: Closes APKT-xxx
For GH issues: closes #...
Showcase (Optional)
If there is a UI change include the screenshots with before and after state.
If new feature is being introduced, include the link to demo recording.
Checklist