Repository navigation
docs(DEVS-1547): add v9 upgrade guide and breaking-change release category - #169
Merged
Merged
Conversation
…se category The docker-registry input was renamed to docker-registries, which breaks existing callers. Document the migration in the README and let release drafter surface breaking PRs via the existing `major` label, so `feature` no longer implies a major bump. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
0x46616c6b
marked this pull request as ready for review
September 30, 2026 11:22
0x46616c6b
requested review from
axdotl,
kaitimmer,
ricoberger and
timkante
and
a balanced review from Copilot
September 30, 2026 11:22
ricoberger
approved these changes
Sep 30, 2026
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The upgrade example is misleading and major-feature PRs would be duplicated across release-note categories.
Review effort: Balanced
Findings: 1
Open (3)
What changed in this PR
Adds v9 migration guidance and configures release categorization/versioning for breaking changes.
Changes:
- Documents the
docker-registry→docker-registriesmigration. - Updates examples to v9.
- Maps release labels to semantic version increments.
| File | Description |
|---|---|
README.md |
Adds v9 upgrade and release guidance. |
.github/release-drafter.yml |
Adds breaking-change categorization and label-based versioning. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
https://mitarbeiterapp.atlassian.net/browse/DEVS-1547
Type of Change
Description
Goal: give callers clear upgrade guidance for the upcoming breaking v9 release (
docker-registryrenamed todocker-registriesin #165).@v9, and a note under "Releasing new versions" to link the upgrade entry in major release notes.majorlabel, which now also triggers the major bump.featuremoves to a minor bump,minor/patchlabels are honoured.How to review: read the upgrade section for accuracy against
action.yml, and check the label mapping in.github/release-drafter.yml.Follow-up before publishing v9: #165 is labelled
featureonly. It needs themajorlabel, otherwise the draft resolves to v8.3.0.Checklist
🤖 Generated with Claude Code