versioning

Enforce Semantic Versioning for Chrono Dawn mod builds via gradle.properties.

Updated Oct 19, 2025
One-click install
npx skills add https://github.com/ksoichiro/ChronoDawn --skill versioning-ksoichiro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: versioning
Source: https://github.com/ksoichiro/ChronoDawn/tree/main/.claude/skills/versioning
Command: npx skills add https://github.com/ksoichiro/ChronoDawn --skill versioning-ksoichiro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill documents and standardizes the versioning process for Chrono Dawn mod releases, ensuring consistent, SemVer-compliant version numbers across development, testing, and production builds.

Core Features & Use Cases

  • Semantic Versioning Overview: explains major.minor.patch rules, prerelease identifiers, and build metadata.
  • Versioning Strategy for Chrono Dawn: outlines development vs release versioning, how to format identifiers (beta, rc, etc.), and how to align with multi-loader builds (Fabric/NeoForge).
  • Build System Integration & Procedures: describes how gradle.properties mod_version is used, how build scripts append metadata to jar names, and how to update docs accordingly.
  • Version Update Procedure: lists steps to update version across documentation, build files, and mod packaging.
  • Use Case: when preparing a new release, follow the guide to increment the correct version, update metadata, and regenerate build artifacts.

Quick Start

Update the mod_version in gradle.properties to begin a new development cycle (e.g., 0.3.0-alpha) and use the dedicated update-version tool to propagate changes across documentation and packaging.

Frequently Asked Questions about versioning

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

FAQPage Schema
How do I manage semantic versioning for mod builds in Gradle?

Semantic versioning for Gradle mod builds is managed by updating the mod_version property in gradle.properties, which build scripts then use to append metadata to jar names and align documentation.

What is the standard versioning strategy for Chrono Dawn prerelease identifiers?

The standard versioning strategy for Chrono Dawn prerelease identifiers uses Semantic Versioning rules, appending specific prerelease identifiers like beta or rc to the major.minor.patch format during development cycles.

How do I update mod version metadata across documentation and packaging?

To update mod version metadata, you change the mod_version in gradle.properties and run a dedicated update-version tool to propagate the new semantic version across documentation and packaging.

Can I use semantic versioning to align multi-loader builds for Fabric and NeoForge?

Yes, the versioning strategy specifies how to format semantic versioning identifiers to align multi-loader builds, ensuring consistent version numbers across Fabric and NeoForge production environments.

When do I need to increment the major, minor, or patch version for a mod release?

You increment the major, minor, or patch version based on Semantic Versioning rules when preparing a new release, guiding version increments to reflect breaking changes, new features, or fixes.

Does the versioning process handle build metadata appended to jar names?

Yes, the versioning process specifies requirements for build metadata and describes how Gradle build scripts automatically append this metadata to generated jar names.