- Notifications
You must be signed in to change notification settings - Fork1.2k
Release process update#587
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
👋 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
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"]5dc5bb7 intomainUh oh!
There was an error while loading.Please reload this page.
* add a new release workflow* improve release.yml to ensure that the ref is up-to-date* add sync workflow
Closes: