docs(release): prepare the 0.1.0 release on the 0.1 train #12

Merged

james.maes merged 1 commits from release/first-release-20261106 into develop 2026-11-06 15:32:27 +00:00

Conversation 0 Commits 1 Files Changed 4

+113 -6

james.maes commented 2026-11-06 14:44:52 +00:00

Owner

Copy link

Copy source

Prepares (does not cut) the first published release of com.kingsrook.qbits:qbit-redis so GG Forge can replace its development pin 0.1.0-forge.54adcfed62b0 with a registry artifact.

• New CHANGELOG.md (0.1.0) and docs/RELEASES.md (shared ci-workflows versioning table, registry consumption, maintainer path including the main fast-forward precondition for the tag run).
• README states the 0.1 train: 0.1.0-RC.1 already published from release/0.1 (tag v0.1.0-RC.1, source 6b0814d); stable 0.1.0 is cut by tagging v0.1.0 there. SNAPSHOT-RELEASE.md marked historical.
• <revision> intentionally stays 0.1.0-SNAPSHOT on develop: the shared workflow computes versions, and a hand-set 0.1.0 here would make the develop run publish 0.2.0-SNAPSHOT.

Validation: ./mvnw.cmd verify on this branch, 33 tests, 0 failures/errors/skips, JaCoCo gates met (real Redis Testcontainers, Docker available). Docs-only change; no source or POM modified.

🤖 Generated with Claude Code

Prepares (does not cut) the first published release of `com.kingsrook.qbits:qbit-redis` so GG Forge can replace its development pin `0.1.0-forge.54adcfed62b0` with a registry artifact. - New `CHANGELOG.md` (0.1.0) and `docs/RELEASES.md` (shared ci-workflows versioning table, registry consumption, maintainer path including the `main` fast-forward precondition for the tag run). - README states the 0.1 train: `0.1.0-RC.1` already published from `release/0.1` (tag `v0.1.0-RC.1`, source `6b0814d`); stable `0.1.0` is cut by tagging `v0.1.0` there. `SNAPSHOT-RELEASE.md` marked historical. - `<revision>` intentionally stays `0.1.0-SNAPSHOT` on develop: the shared workflow computes versions, and a hand-set `0.1.0` here would make the develop run publish `0.2.0-SNAPSHOT`. Validation: `./mvnw.cmd verify` on this branch, 33 tests, 0 failures/errors/skips, JaCoCo gates met (real Redis Testcontainers, Docker available). Docs-only change; no source or POM modified. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

james.maes added 1 commit 2026-11-06 14:45:40 +00:00

docs(release): prepare the 0.1.0 release on the 0.1 train ... e267f4f84a

Add CHANGELOG.md for the first published release and docs/RELEASES.md
describing the shared ci-workflows versioning (develop SNAPSHOT,
release/0.1 RC.N, tag vX.Y.Z stable), registry consumption and the
maintainer path. README now states the 0.1 train (0.1.0-RC.1 published,
0.1.0 cut by tag) instead of the coordinated snapshot; SNAPSHOT-RELEASE.md
is marked historical. The POM revision stays 0.1.0-SNAPSHOT on develop
because the workflow owns version computation.

Verified locally: ./mvnw.cmd verify, 33 tests, 0 failures/errors/skips,
JaCoCo gates met.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

james.maes merged commit 63e42c8153 into develop 2026-11-06 15:32:27 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

bug

Something isn't working

dependencies

documentation

Improvements or additions to documentation

duplicate

This issue or pull request already exists

enhancement

New feature or request

good first issue

Good for newcomers

help wanted

Extra attention is needed

invalid

This doesn't seem right

question

Further information is requested

secuurity

wontfix

This will not be worked on

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

forge-recovery (Forge Recovery) james.maes (James Maes)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-redis#12