The version was bumped per deployment, and build.gradle.kts said so:
"bump at least the patch version for every deployment — and only then,
not per commit". PR#50 and PR#51 were merged and deployed while both
calling themselves v1.7.0, so the running instance reported a version
that named neither of them. A version that cannot tell two deployments
apart is not identifying what runs, which was the point of having one.
1.8.0 is a minor because the most significant thing it carries is new
behaviour: werkdock's import verb and the stale-binary rebuild of PR#50.
Its release-notes entry covers PR#50 and PR#51 together and says that
this is the last release assembled that way.
The rule lived in four places — build.gradle.kts, AGENTS.md,
docs/prs/README.md and the pr-doc skill — so all four now say the same
thing: every PR bumps the version, patch for a fix and minor for new
behaviour, and brings its own release-notes entry. The comment above version names the failure that produced the rule, so the reason stays
next to the line it governs. The pure-release exception survives as the
rare case rather than the normal one.
The version was bumped per deployment, and build.gradle.kts said so:
"bump at least the patch version for every deployment — and only then,
not per commit". PR#50 and PR#51 were merged and deployed while both
calling themselves v1.7.0, so the running instance reported a version
that named neither of them. A version that cannot tell two deployments
apart is not identifying what runs, which was the point of having one.
1.8.0 is a minor because the most significant thing it carries is new
behaviour: werkdock's import verb and the stale-binary rebuild of PR#50.
Its release-notes entry covers PR#50 and PR#51 together and says that
this is the last release assembled that way.
The rule lived in four places — build.gradle.kts, AGENTS.md,
docs/prs/README.md and the pr-doc skill — so all four now say the same
thing: every PR bumps the version, patch for a fix and minor for new
behaviour, and brings its own release-notes entry. The comment above
`version` names the failure that produced the rule, so the reason stays
next to the line it governs. The pure-release exception survives as the
rare case rather than the normal one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The version was bumped per deployment, and build.gradle.kts said so:
"bump at least the patch version for every deployment — and only then,
not per commit". PR#50 and PR#51 were merged and deployed while both
calling themselves v1.7.0, so the running instance reported a version
that named neither of them. A version that cannot tell two deployments
apart is not identifying what runs, which was the point of having one.
1.8.0 is a minor because the most significant thing it carries is new
behaviour: werkdock's import verb and the stale-binary rebuild of PR#50.
Its release-notes entry covers PR#50 and PR#51 together and says that
this is the last release assembled that way.
The rule lived in four places — build.gradle.kts, AGENTS.md,
docs/prs/README.md and the pr-doc skill — so all four now say the same
thing: every PR bumps the version, patch for a fix and minor for new
behaviour, and brings its own release-notes entry. The comment above
`version` names the failure that produced the rule, so the reason stays
next to the line it governs. The pure-release exception survives as the
rare case rather than the normal one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mi
merged commit e07ab74082 into main2026-09-11 06:52:07 +02:00
mi
deleted branch release/1.8.0-and-bump-rule2026-09-11 06:52:07 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The version was bumped per deployment, and build.gradle.kts said so:
"bump at least the patch version for every deployment — and only then,
not per commit". PR#50 and PR#51 were merged and deployed while both
calling themselves v1.7.0, so the running instance reported a version
that named neither of them. A version that cannot tell two deployments
apart is not identifying what runs, which was the point of having one.
1.8.0 is a minor because the most significant thing it carries is new
behaviour: werkdock's import verb and the stale-binary rebuild of PR#50.
Its release-notes entry covers PR#50 and PR#51 together and says that
this is the last release assembled that way.
The rule lived in four places — build.gradle.kts, AGENTS.md,
docs/prs/README.md and the pr-doc skill — so all four now say the same
thing: every PR bumps the version, patch for a fix and minor for new
behaviour, and brings its own release-notes entry. The comment above
versionnames the failure that produced the rule, so the reason staysnext to the line it governs. The pure-release exception survives as the
rare case rather than the normal one.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com