Skip to content

Conversation

@kejadlen
Copy link
Collaborator

Summary

Replaces patch-increment versioning with calendar versioning. Each release now
uses the format YYYY.M.patch (e.g., 2024.12.1), where the patch number
resets monthly and increments for each release within that month.

The workflow calculates the next version by scanning existing tags for the
current month rather than relying on cargo-release's automatic patch bump.


Assisted-by: Claude (Anthropic)

Enables multiple releases per month with incrementing patch number.
Tag lookup avoids external state.

Assisted-by: Claude Opus 4.5 via Claude Code
@kejadlen kejadlen marked this pull request as ready for review December 19, 2025 23:21
@kejadlen kejadlen requested a review from a team as a code owner December 19, 2025 23:21
Copy link
Collaborator

@rubberduck203 rubberduck203 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like that will work.
It's been bothering me for a while, so thanks!

@rubberduck203 rubberduck203 enabled auto-merge (squash) December 20, 2025 14:17
@rubberduck203 rubberduck203 merged commit 54c8ffe into oscope-dev:main Jan 7, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants