version-bumped

Checks that the current Git branch's Gradle publishing version is strictly greater than the base ref.

2|Updated May 28, 2021
One-click install
npx skills add https://github.com/SpineEventEngine/validation --skill version-bumped
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bumped
Source: https://github.com/SpineEventEngine/validation/tree/main/.agents/skills/version-bumped
Command: npx skills add https://github.com/SpineEventEngine/validation --skill version-bumped

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill verifies that a feature branch has advanced its publishing version so that local/published artifacts for the same version cannot be unintentionally overwritten.

Core Features & Use Cases

  • Strict version-advance guard: Blocks when version.gradle.kts’s publishing version is unchanged or decreased compared to the configured base ref.
  • Deterministic version key discovery: Extracts the publishing version key from Gradle build scripts (or uses VERSION_BUMPED_KEY when provided) and compares versions via a strict greater-than check.
  • Optional auto-recovery workflow: When blocked (exit code 1), it invokes /bump-version and then re-runs the check once to confirm recovery.

Use case: On a feature branch with commits that include both code changes and a retry-ready version bump, ensure publishToMavenLocal won’t overwrite the artifact version that integration tests in consumer repos may rely on.

Quick Start

Run version-bumped on the current branch to confirm the Gradle publishing version is strictly greater than the base ref, or auto-recover by triggering the bump when it is not.

Frequently Asked Questions about version-bumped

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent accidental Maven Local artifact overwrites in a Gradle build?

You prevent Maven Local overwrites by running a deterministic check that blocks publishing when the version in version.gradle.kts is unchanged or decreased compared to a base Git ref.

How does version bumping work with Git branch divergence for Kotlin Gradle repositories?

It works by extracting the publishing version key from Gradle build scripts and comparing it against a base ref using a strict greater-than check to guarantee safe artifact publishing.

Can I automatically trigger a version bump when a CI guardrail blocks my build?

Yes, when blocked by the CI guardrail, you can automatically invoke the bump-version command and re-run the verification check exactly once to confirm recovery before publishing.

Does this version check work with Java and Kotlin Gradle projects?

Yes, the version check applies to publishing and build workflows in Java and Kotlin Gradle repositories where version increments must track branch divergence for Maven Local consumers.

What are the limitations of using a strict greater-than check for Gradle publishing versions?

The limitation is that it blocks execution on unchanged or decreased versions, requiring an explicit version bump before any artifact publishing can proceed safely.