version-bumped

name

version-bumped

description

Verifies the current branch has bumped `version.gradle.kts` strictly above the base ref; runs the `bump-version` skill to auto-recover if not. Composable: other modifying skills (`dependency-update`, `bump-gradle`, `java-to-kotlin`, `move-files`) call this as their final step so a `./gradlew build` or `publishToMavenLocal` can never overwrite a previously published Maven Local artifact that integration tests in consumer repos depend on.

Ensure version is bumped

This skill is the agent-facing wrapper around .agents/skills/version-bumped/scripts/version-bumped.sh. The script is the source of truth for "has this branch advanced the version vs base?"; this skill just runs it and, if it fails, runs the bump-version skill and re-runs to confirm.

The same logic is enforced as a hook (.agents/scripts/publish-version-gate.sh) that fires before any ./gradlew … (build|publish|publishToMavenLocal) invocation, so even direct gradle calls cannot bypass it. This skill exists for the cooperative path — other skills calling it before they finish, so the user is never surprised by a blocked gradle command later.

The premise is simple: any feature branch is a candidate for publishing, even when the only change is the version bump itself (sometimes the bump is the entire change, used to retry a publish that failed because Maven repositories were overloaded). So if the branch differs from base at all, the version must advance.

When to use

• Automatically: as the final step of any skill that may change files on the branch.
• Manually (version-bumped): before running ./gradlew build or ./gradlew publishToMavenLocal on a feature branch when you are not sure whether the version has already been bumped.

Procedure

1. Run the deterministic check:

   .agents/skills/version-bumped/scripts/version-bumped.sh
   

   Honor VERSION_BUMPED_BASE if the user has set a non-default base ref (e.g. origin/master, or a release branch).

2. Interpret the exit code:

   • 0 — Done. Either the repository has no root version.gradle.kts (the version check is N/A), the branch has no diff vs base, or the version is already strictly greater. Report a one-line confirmation and stop.
   • 1 — Block. The script's stderr explains which check failed. Proceed to step 3.
   • 2 — Configuration error (no merge-base, parse failure on version.gradle.kts). Do not run the bump-version skill automatically. Surface the script's stderr to the user and stop.

3. On exit 1, run the bump-version skill to perform the actual bump. That skill owns the policy (snapshot numbering, the commit subject, the rebuild, dependency-report regeneration, and the conflict rule). Do not duplicate its work here.

4. After bump-version finishes, re-run the deterministic check. If it now passes, report the new version on the branch. If it still fails, surface the stderr unchanged and stop — do not loop.

Why this skill is separate from bump-version

bump-version is the action (it edits version.gradle.kts, commits, rebuilds, may commit reports). version-bumped is the guard (read-only check, optional auto-recovery). Skills that want to say "make sure the branch has a bumped version" should call version-bumped, not bump-version. bump-version now runs its own idempotency gate (the same version-bumped.sh check) and stops without committing when the branch is already ahead of base, so a stray direct call no longer double-bumps. Still prefer the guard for the "ensure bumped" intent: it expresses that intent directly and skips the action entirely when the bump is already done.

Relationship to checkVersionIncrement

The Gradle task checkVersionIncrement (in buildSrc/.../publish/) asks a different question: "is this version already in the remote Maven metadata?" It runs on GitHub Actions feature-branch pushes and fetches the Spine SDK Artifact Registry. The two checks are complementary — neither subsumes the other.

See also

• .agents/guidelines/version-policy.md — when the version gate applies.
• .agents/skills/bump-version/SKILL.md — the bump procedure itself.
• .agents/skills/pre-pr/SKILL.md — uses the same check at PR time (step 2).
• .agents/skills/version-bumped/scripts/version-bumped.sh — the deterministic check.
• .agents/scripts/publish-version-gate.sh — the hook that enforces the rule on ./gradlew invocations.