bump-version

Update Spine project versions in version.gradle.kts and commit under strict rules.

2|Updated May 28, 2021

Search Tags:#semantic versioning #git commit #gradle #version bump #release process #CI guardrails #dependency reports

Ready to run

npx skills add https://github.com/SpineEventEngine/validation --skill bump-version-spineeventengine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/SpineEventEngine/validation/tree/main/.agents/skills/bump-version
Command: npx skills add https://github.com/SpineEventEngine/validation --skill bump-version-spineeventengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents CI failures and publishing conflicts by safely bumping the Spine SDK version in version.gradle.kts according to the project’s versioning policy.

Core Features & Use Cases

It updates the correct version source value (including cases where versionToPublish is derived from another extra property) and applies the correct snapshot-line or release-line increment rules. It enforces safe commit behavior by allowing exactly one authorized commit that stages only version.gradle.kts and uses the required commit subject format. It then rebuilds the project to regenerate dependency/pom reports and provides validation steps to confirm the branch state after the bump.

Quick Start

Run the bump-version skill on the repository root to update version.gradle.kts, commit the bump with the required subject, rebuild with ./gradlew clean build, and verify the resulting branch changes.

Frequently Asked Questions about bump-version

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

FAQPage Schema

How do I bump the Spine SDK version in version.gradle.kts for a release?▼

The bump-version process edits version.gradle.kts to update the correct source value, applies the appropriate snapshot or release increment rules, and commits the change with a strict subject format.

How does Version Guard enforce semantic versioning during the release process?▼

Version Guard enforces semantic versioning by preventing version repetition and verifying version correctness across Maven publishing during CI and release-prep workflows.

Can I stage additional files when committing a version bump in CI?▼

No, the version bump commit must stage only version.gradle.kts and is limited to exactly one authorized commit to enforce safe CI behavior and prevent publishing conflicts.

What is the best way to verify a Gradle version bump before publishing?▼

After bumping the version, rebuild the project with ./gradlew clean build to regenerate dependency and POM reports, then verify the branch state using git diff and version-subject checks.

Why does versionToPublish need to be updated separately in version.gradle.kts?▼

When versionToPublish is derived from another extra property, updating the underlying source value ensures the derived publishing version remains correct and compliant with the project's versioning policy.