Release process update #587
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
|
👋 Hi there! It looks like this PR is targeting the If this is a bug fix that requires a patch release __ (e.g., a critical bug that needs to be fixed before the next release), please leave the base branch as You can change this by:
Thanks for your contribution! 🚀 |
There was a problem hiding this comment.
Pull Request Overview
This PR updates the release process by clarifying contributor instructions and adding new automation workflows for branch synchronization, releasing, and base branch checking.
- Updates CONTRIBUTING.md to instruct contributors to open pull requests against the next branch.
- Introduces new GitHub Actions workflows for syncing the next branch with main, automating releases, checking PR base branches, and publishing Docker images.
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| CONTRIBUTING.md | Added instructions to target the next branch when submitting pull requests. |
| .github/workflows/sync-next-branch.yml | New workflow to automatically sync the next branch with main daily. |
| .github/workflows/release.yml | New automated release workflow including tag validation, branch checks, and PR creation. |
| .github/workflows/pr-base-check.yml | New workflow to alert contributors when targeting the main branch instead of next. |
| .github/workflows/docker-publish.yml | Updated branch filters to include both main and next for Docker publishing. |
Comments suppressed due to low confidence (2)
CONTRIBUTING.md:22
- [nitpick] The added instruction clearly directs contributors to use the 'next' branch. Consider reviewing the rest of the documentation to ensure all branch references are consistent.
> **Important**: Please open your pull request against the `next` branch, not `main`. The `next` branch is where we integrate new features and changes before they are merged to `main`.
.github/workflows/docker-publish.yml:12
- With the updated branch filter including 'next', double-check that Docker publish triggers are intended on both branches to avoid unintended deployments.
branches: ["main", "next"]
SamMorrowDrums
added a commit
that referenced
this pull request
Jun 26, 2025
* add a new release workflow * improve release.yml to ensure that the ref is up-to-date * add sync workflow
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.
Closes: