calver-release

Schedule and enforce CalVer releases with automated changelog and git tag updates.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/kabaka/cpap-analyzer --skill calver-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: calver-release
Source: https://github.com/kabaka/cpap-analyzer/tree/main/.github/skills/calver-release
Command: npx skills add https://github.com/kabaka/cpap-analyzer --skill calver-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CalVer release processes standardize and automate version tagging, reducing confusion and errors when releasing software.

Core Features & Use Cases

  • Enforce and communicate a calendar-based versioning scheme (YYYY.0M.MICRO) across the team.
  • Automate updates to CHANGELOG.md and the package.json version, and create git tags for each release.
  • Support monthly or milestone-based release cadences with repeatable workflows.

Quick Start

Run the CalVer release script to generate and tag the current month’s version

Frequently Asked Questions about calver-release

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

FAQPage Schema
How do I automate CalVer versioning for monthly software releases?▼

To automate CalVer versioning for monthly releases, you can use a script that parses dates, updates package.json and CHANGELOG.md, and creates git tags. This enforces a consistent YYYY.0M.MICRO versioning scheme across your project.

What is the best way to manage a calendar-based versioning workflow?▼

The best way to manage calendar-based versioning is to enforce a repeatable workflow that automatically generates version tags based on the release date, ensuring consistent versioning and reducing manual errors during software deployments.

How do I update package.json and CHANGELOG.md with a new release tag?▼

You can update package.json and CHANGELOG.md by running a release script that parses the current date, applies the CalVer format, modifies the files, and commits the changes with a new git tag for the release.

Does calendar versioning work for quarterly release cadences?▼

Yes, calendar versioning works for quarterly release cadences. It supports milestone-based release schedules by parsing dates to generate appropriate calendar-based tags, providing a repeatable workflow for both monthly and quarterly software releases.

Why use CalVer instead of semantic versioning for scheduled releases?▼

CalVer is used instead of semantic versioning for scheduled releases because it communicates the release timeline directly through the version number using a YYYY.0M.MICRO format, making it easier to track when a specific version was deployed.

When should I not use calendar versioning for my project?▼

You should not use calendar versioning for projects lacking a predictable monthly or quarterly release schedule, as CalVer requires consistent calendar-based milestones to effectively parse dates and automate the tagging workflow.