Skip to content

Release process update #588

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 26, 2025
Merged

Release process update #588

merged 1 commit into from
Jun 26, 2025

Conversation

SamMorrowDrums
Copy link
Collaborator

Closes:

@Copilot Copilot AI review requested due to automatic review settings June 26, 2025 15:26
@SamMorrowDrums SamMorrowDrums requested a review from a team as a code owner June 26, 2025 15:26
Copy link
Contributor

@Copilot Copilot AI left a 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 and development workflow by providing clearer guidelines for contributors and automating branch synchronization and release creation via GitHub workflows.

  • Updated CONTRIBUTING.md to instruct contributors to target the next branch for pull requests.
  • Added a new workflow (sync-next-branch.yml) to automatically keep the next branch synchronized with main.
  • Introduced a release workflow (release.yml) along with additional workflows (pr-base-check.yml and docker-publish.yml) to enforce branch targeting and streamline releases.

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 Instructs contributors to open PRs against the next branch.
.github/workflows/sync-next-branch.yml Automates daily sync of the next branch with main.
.github/workflows/release.yml Automates release creation with tag validation, branch checks, and PR creation.
.github/workflows/pr-base-check.yml Adds a reminder comment to PRs targeting main to switch to the next branch.
.github/workflows/docker-publish.yml Extends Docker publish triggers to include changes from the next branch.
Comments suppressed due to low confidence (1)

.github/workflows/pr-base-check.yml:27

  • The inline markdown formatting in this comment contains extra underscores that may lead to unintended emphasis. Consider revising the syntax (e.g., using proper bold or italic markdown) so that the message renders clearly.
            __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 \`main\`.__

@SamMorrowDrums SamMorrowDrums force-pushed the release-process-update branch from 20ddb93 to 4305a77 Compare June 26, 2025 15:27
Copy link

👋 Hi there!

It looks like this PR is targeting the main branch. To help maintain our development workflow, please change the base reference to next instead.

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 main.__

You can change this by:

  1. Clicking the "Edit" button next to the PR title
  2. Changing the base branch from main to next
  3. Clicking "Update pull request"

Thanks for your contribution! 🚀

@SamMorrowDrums SamMorrowDrums merged commit b9a5f2c into main Jun 26, 2025
14 of 16 checks passed
@SamMorrowDrums SamMorrowDrums deleted the release-process-update branch June 26, 2025 15:28
SamMorrowDrums added a commit that referenced this pull request Jun 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant