Skip to content

fix(release): set initial-version only before the first release tag - #30

Merged
vannt-dev merged 2 commits into
mainfrom
fix/initial-version-only-before-first-release
Sep 28, 2026
Merged

vannt-dev merged 2 commits into
mainfrom
fix/initial-version-only-before-first-release

Conversation

@vannt-dev

Copy link
Copy Markdown
Owner

Found while updating the pilots to 1.4.0: repokeeper-demo-kotlin (tag v1.0.0, manifest 1.0.0) got initial-version: 0.1.0. Its gradle.properties still reads version=0.0.0, because release-please's generic updater needs x-release-please markers there, and that version is the seed.

initial-version is now added only when the seed is 0.0.0 and the repository has no vX.Y.Z tag. Standard 1.4.1. New test cases cover a 0.0.0 version file with and without a release tag.

Checks: typecheck, biome, 278/278 tests, repokeeper check.

🤖 Generated with Claude Code

A version file release-please never bumps, such as gradle.properties
without x-release-please markers, still reads 0.0.0 after v1.0.0, so
repokeeper-demo-kotlin got initial-version despite its release. A release
tag now rules it out. The standard moves to 1.4.1.
@vannt-dev
vannt-dev merged commit 3819874 into main Sep 28, 2026
5 checks passed
@vannt-dev
vannt-dev deleted the fix/initial-version-only-before-first-release branch September 28, 2026 14:31
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.

1 participant