Repository navigation
docs(release-skill): collapse notes by library identity and derive versions from project.yml - #256
Conversation
…rsions from project.yml Aligns this repo's release skill with the fixes found while cutting a release in nifi-extensions, where four dependency entries shipped duplicated in the notes. ## Release-note grouping The collapse rule keyed on **PR-title equality**, so titles differing only by a directory or coordinate suffix matched nothing and both lines survived. - **Collapse by library identity**, spelling out the three shapes that occur: version chains, the same library bumped in several modules/directories, and one upstream release landing as several coordinates (e.g. a version property *and* a BOM/parent). - **Recover versions the title omits** — Dependabot truncates a title to `bump <lib> in /<dir>` when several deps must move together; the versions are then only in the PR body. No dependency line may ship without a version range. - **Resolved a contradiction**: the old rules required both rewriting the version range when collapsing and preserving each line verbatim. The collapse rules now explicitly win. - **Added a mandatory duplicate check** before `gh release edit`: every library must appear exactly once. This catches the above mechanically instead of by careful reading. ## Versions derived from `.github/project.yml` The skill restated `current-version` / `next-version` inline and built its examples around that hardcoded pair, so every release made the skill stale. Both numbers are now read from `.github/project.yml`, and the branch-name and `project.yml`-edit examples use placeholders. The repo's own versioning policy is preserved, expressed symbolically. Documentation-only change under `.claude/`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QDdBo9BsuMyifN5g6551v7
There was a problem hiding this comment.
Sorry @OliverWolffGIP, you've used your own review budget of 250,000 diff characters for the last 7 days.
You can request another review in 2 days and 13 hours by commenting @sourcery-ai review. Upgrade to get a review now.
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: cuioss/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Aligns this repo's release skill with the fixes found while cutting a release in
nifi-extensions, where four dependency entries shipped duplicated in the notes.
Release-note grouping
The collapse rule keyed on PR-title equality, so titles differing only by a
directory or coordinate suffix matched nothing and both lines survived.
chains, the same library bumped in several modules/directories, and one upstream
release landing as several coordinates (e.g. a version property and a BOM/parent).
bump <lib> in /<dir>when several deps must move together; the versions are thenonly in the PR body. No dependency line may ship without a version range.
when collapsing and preserving each line verbatim. The collapse rules now explicitly win.
gh release edit: every library mustappear exactly once. This catches the above mechanically instead of by careful reading.
Versions derived from
.github/project.ymlThe skill restated
current-version/next-versioninline and built its examplesaround that hardcoded pair, so every release made the skill stale. Both numbers are now
read from
.github/project.yml, and the branch-name andproject.yml-edit examples useplaceholders. The repo's own versioning policy is preserved, expressed symbolically.
Documentation-only change under
.claude/.🤖 Generated with Claude Code
https://claude.ai/code/session_01QDdBo9BsuMyifN5g6551v7