Add micro component to calver to allow multiple same-day releases #137

New issue

Closed

opened 2026-08-12 03:08:50 +00:00 by agent-pi · 1 comment

agent-pi commented

2026-08-12 03:08:50 +00:00

Collaborator

The current calver scheme YYYY.M.D (e.g. 2026.8.12) blocks a second release on the same date — just release refuses to run when $NEXT == $CURRENT. There's no way to release twice on the same day without manual tag surgery and PyPI/container conflicts.

Switch to YYYY.M.D.N where N starts at 1 and increments for each release on the same day.

Changes:

pyproject.toml: version format + bump-my-version parse/serialize
justfile: micro-aware release logic (same-day → increment micro, new-day → reset to .1)
Release-Notes.md.template: version placeholder

The current calver scheme `YYYY.M.D` (e.g. `2026.8.12`) blocks a second release on the same date — `just release` refuses to run when `$NEXT == $CURRENT`. There's no way to release twice on the same day without manual tag surgery and PyPI/container conflicts. Switch to `YYYY.M.D.N` where N starts at 1 and increments for each release on the same day. Changes: - `pyproject.toml`: version format + bump-my-version parse/serialize - `justfile`: micro-aware release logic (same-day → increment micro, new-day → reset to .1) - `Release-Notes.md.template`: version placeholder

agent-pi commented

2026-08-12 03:08:58 +00:00

Author

Collaborator

Plan

Root cause: YYYY.M.D calver has no sub-day resolution. The just release guard if [[ "$NEXT" == "$CURRENT" ]] explicitly blocks a second release on the same date.

Approach: Switch to YYYY.M.D.N — micro component always present, starts at .1 for the first release of each day, increments for subsequent same-day releases.

Changes:

pyproject.toml — version = "2026.8.12.1", bump-my-version parse/serialize updated, files entries unchanged (they already use {current_version}/{new_version}).
justfile — release recipe: instead of blocking same-day, parse the current version's date and micro. If today's date matches the current date, increment micro; otherwise set to TODAY.1.
Release-Notes.md.template — cosmetic: YYYY.MM.DD → YYYY.MM.DD.N placeholder (the actual version is filled by bump-my-version).

Branch: feat/issue-137-micro-calver

Commits:

🧱 Add micro component to calver versioning

PR: fj pr create targeting main

**Plan** **Root cause:** `YYYY.M.D` calver has no sub-day resolution. The `just release` guard `if [[ "$NEXT" == "$CURRENT" ]]` explicitly blocks a second release on the same date. **Approach:** Switch to `YYYY.M.D.N` — micro component always present, starts at `.1` for the first release of each day, increments for subsequent same-day releases. **Changes:** 1. **`pyproject.toml`** — `version = "2026.8.12.1"`, bump-my-version parse/serialize updated, files entries unchanged (they already use `{current_version}`/`{new_version}`). 2. **`justfile`** — `release` recipe: instead of blocking same-day, parse the current version's date and micro. If today's date matches the current date, increment micro; otherwise set to `TODAY.1`. 3. **`Release-Notes.md.template`** — cosmetic: `YYYY.MM.DD` → `YYYY.MM.DD.N` placeholder (the actual version is filled by bump-my-version). **Branch:** `feat/issue-137-micro-calver` **Commits:** - :bricks: Add micro component to calver versioning **PR:** `fj pr create` targeting `main`

agent-pi referenced this issue from a commit

2026-08-12 03:10:21 +00:00

:bricks: Add micro component to calver versioning

agent-pi referenced this issue from a pull request that will close it,

2026-08-12 03:10:35 +00:00

Add micro component to calver for same-day releases #138

agent-pi referenced this issue from a commit

2026-08-12 03:26:43 +00:00

:bricks: Add micro component to calver versioning