Skip to content

Require an explicit release channel - #30

Open
nodeselector wants to merge 1 commit into
mainfrom
nodeselector-publish-release-candidate
Open

Require an explicit release channel#30
nodeselector wants to merge 1 commit into
mainfrom
nodeselector-publish-release-candidate

Conversation

@nodeselector

Copy link
Copy Markdown
Collaborator

No description provided.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings September 8, 2026 20:27
@nodeselector
nodeselector requested a review from a team as a code owner September 8, 2026 20:27

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

The implementation, tests, and release documentation consistently enforce explicit channel selection.

Review tier: Balanced
Findings: None

What changed in this PR

Requires maintainers to explicitly select a stable or release-candidate channel when cutting Go module releases.

Changes:

  • Adds mandatory --stable or --rc validation.
  • Updates release documentation and tests.
File Description
script/​release Requires an explicit release channel.
script/​release_test Tests stable releases and missing-channel failure.
RELEASING.md Documents the new --stable usage.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

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.

2 participants