Skip to content

Derive the release bump from a per-item breaking flag - #918

Merged
LikeTheSalad merged 2 commits into
mainfrom
enhancement/android-release-breaking-flag
Sep 28, 2026
Merged

LikeTheSalad merged 2 commits into
mainfrom
enhancement/android-release-breaking-flag

Conversation

@LikeTheSalad

@LikeTheSalad LikeTheSalad commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

These changes remove the bump input from the prepare release workflow. This makes the workflow simpler and will also help with a follow-up "patch release" support path.

This bump input was mostly to help prepare a major release, as by default it was always "minor", but since major releases aren't that common, and they also depend on there being a breaking change, the major version bump can be signaled by a breaking change in the release notes instead. This makes the overall process less error-prone in case someone accidentally chooses the "major" version bump input option when a minor release was due.

Each release-note item may carry a boolean breaking flag, and any flagged item makes the release major, otherwise it is minor. The render script writes the [Breaking] prefix from the flag, sorts flagged items first, and rejects a message that already starts with the prefix. The release guide and wizard are also updated.

Prepare release no longer takes a bump input. Each release-note item may
carry a boolean breaking flag; any flagged item makes the release major,
otherwise it is minor. The render script writes the [Breaking] prefix from
the flag, sorts flagged items first, and rejects a message that already
starts with the prefix. The release guide and wizard follow.
@LikeTheSalad
LikeTheSalad requested a lite review from Copilot September 24, 2026 14:27
@github-actions

Copy link
Copy Markdown

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

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

🟡 Changes recommended

Documentation should accurately describe the renderer’s start-of-message prefix validation.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 2 Low severity

Open (2)
What changed in this PR

This PR derives release bumps from per-item breaking flags instead of a workflow-level input.

Changes:

  • Removes the manual bump input.
  • Validates, sorts, and renders breaking release notes.
  • Updates release scripts, documentation, wizard guidance, and sample data.
File Summary
skills/​android-release-wizard/​SKILL.md Updates wizard guidance for breaking flags.
RELEASING.md Documents flag-based release versioning.
.github/​workflows/​prepare-release.yml Removes the bump input.
.github/​scripts/​release/​sample.json Demonstrates breaking-note metadata.
.github/​scripts/​release/​render-release-notes.sh Validates, sorts, and renders release notes.
.github/​scripts/​release/​prepare-release.sh Derives the release bump from note flags.

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

Comment thread RELEASING.md Outdated
Comment thread skills/android-release-wizard/SKILL.md Outdated
The guide and wizard described the check as rejecting any occurrence of
[Breaking] in a message. The render script rejects only a message that
starts with it, which is the intended rule.

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

🔵 Needs a closer look

Release automation changes affect versioning and workflow behavior and warrant final human review.

Review effort: Lite
Findings: None

Resolved since last review (2)

@LikeTheSalad
LikeTheSalad marked this pull request as ready for review September 24, 2026 14:54
@LikeTheSalad
LikeTheSalad requested review from a team as code owners September 24, 2026 14:54

@vishaangelova vishaangelova left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@LikeTheSalad
LikeTheSalad merged commit 1fe46f7 into main Sep 28, 2026
15 checks passed
@LikeTheSalad
LikeTheSalad deleted the enhancement/android-release-breaking-flag branch September 28, 2026 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants