#162 - Adopt frankenbit/release-toolkit — adds structured release-cut + closes #157 - frankenbit/cellblock

No Branch/Tag specified

main

release-prep/rolling

i/rt806-secrets-inherit

i/repin-release-toolkit-v0.42.0

i/280-fragment-check-wiring

i/release-toolkit-v0.18.0-bump

i/cellblock-release-toolkit-adoption-v0.10.1

i/162-release-toolkit-substrate-prep

i/145-boot-auto-resume

i/149-force-take-resume

i/142-cellmate-found-back-cancel

i/151-cancel-protocol

i/160-nav-arrange-await

i/155-disconnect-overlay-debounce

i/146-lobby-nameplate-margin

i/147-version-display

i/139-survivor-overlay

i/139-reconnecting-overlay

i/144-history-trap-depth

i/141-highscores-clickthrough

i/130-live-stats-wire

i/113-netstub-migration

i/115-reconnect-via-resume

i/88-checkin-touch-back

i/104-fold-invariant-test

i/104-108-120-mobile-portrait-polish

i/101-cabinet-bezel

i/123-localstorage-resume-token

i/103-121-input-label-polish

i/102-cue-logic-test

i/102-celebration-cue

i/122-keepalive-tightening

i/111-server-gravity-hold

i/100-tagline-contrast

i/99-mobile-versus-layout

i/cellblock-83-video-on-failure

i/109-back-button-trap

i/93-ws-onclose-handler

i/92-ws-mock-harness

i/110-countdown-input-lock

i/97-initials-focus-capture

i/98-eligibility-deconflation

i/87-abort-forfeit

i/87-server-forfeit

i/91-solo-playagain-mode

i/85-lobby-esc-back

i/86-durationms-int

i/81-keyboard-nav-harness

i/73-landscape-initials

i/76-admin-redact-endpoint

i/66-checkin-name-input

i/59-initials-scroller

i/54-leaderboard-metrics

i/51-remove-dead-attachinput

i/69-block-pinch-zoom

i/62-portrait-gameover

i/57-portrait-solo-layout

i/64-rapid-tap-zoom

i/60-canvas-text-selection

i/56-ios-audio-unlock

i/53-next-queue

i/capture-bg-harness

i/49-animated-bg

i/28-leaderboard-wire

i/26-validation-harnesses

i/28-leaderboard-store

i/31-soft-drop-tick

i/28-leaderboard-ui-shell

i/39-nextqueue-contract

i/39-nextqueue

i/33-bgm-gain

i/16-solo-mode

i/35-keyboard-parity

i/32-spectate-exit

i/15-bgm

i/16-solo-server-endpoint

i/21-ci-race-guard

i/8-smooth-fall

i/16-solo-sfx-best

i/16-solo-hide

i/9-dissolve

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

frankenbit/cellblock#162

quartermaster commented

2026-06-24 09:06:51 +02:00

Owner

Scope

Adopt frankenbit/release-toolkit (alcatraz-infra#65 + Bosun 13b1) as cellblock's release-cut machinery. Closes cellblock#157 by adoption (the toolkit's _manifest-check.yml reusable is the manifest-vs-tag CI check #157 wants).

Blocked on: frankenbit/release-toolkit v0.1.0 cut.

Current state

v1.0.0 cut manually (PR #156 caught manifest-vs-tag mismatch opportunistically)
No structured CHANGELOG (commit history is the cadence record)
No release-CI check (#157 tracker filed)
Future cuts need both substrate-honesty + author-cadence

Acceptance criteria

Add release-toolkit.yml config in repo root with release_type: node, version_files: [client/package.json, server/version.go] (if present), changelog: CHANGELOG.md
Add changelog.d/.keep to seed the fragment directory
(Optional) Backfill retro-fragments for v1.0.0's substantive content as a one-off
Add CHANGELOG.md skeleton with ## [Unreleased] section + ## [v1.0.0] for the already-cut release
Add consumer workflow .forgejo/workflows/release.yml referencing _release-prep.yml@vX.Y.Z
Add consumer workflow .forgejo/workflows/release-draft.yml referencing _release-draft.yml@vX.Y.Z
Add consumer workflow .forgejo/workflows/release-publish.yml referencing _release-publish.yml@vX.Y.Z
Add consumer workflow .forgejo/workflows/manifest-check.yml referencing _manifest-check.yml@vX.Y.Z for PR CI
Document fragment + conventional-commits convention in cellblock/CLAUDE.md for chamber authors
Cut v1.0.1 (or v1.1.0) using the toolkit as the first end-to-end validation
Close #157 (manifest-vs-tag CI check) — this issue's manifest-check.yml adoption IS the resolution

Open questions

Do we backfill v1.0.0's CHANGELOG section retroactively, or start from v1.0.1 cleanly? (Operator preference TBD; either works.)
Does cellblock want conventional-commits adoption ALSO (Shipwright's chamber-author shape) or just fragments-for-rich-prose? Both are supported by the toolkit.

— QM, 2026-06-24, per Bosun ratification 13b1.

## Scope Adopt `frankenbit/release-toolkit` (alcatraz-infra#65 + Bosun 13b1) as cellblock's release-cut machinery. **Closes cellblock#157** by adoption (the toolkit's `_manifest-check.yml` reusable is the manifest-vs-tag CI check #157 wants). Blocked on: frankenbit/release-toolkit v0.1.0 cut. ## Current state - v1.0.0 cut manually (PR #156 caught manifest-vs-tag mismatch opportunistically) - No structured CHANGELOG (commit history is the cadence record) - No release-CI check (#157 tracker filed) - Future cuts need both substrate-honesty + author-cadence ## Acceptance criteria - [ ] Add `release-toolkit.yml` config in repo root with `release_type: node`, `version_files: [client/package.json, server/version.go]` (if present), `changelog: CHANGELOG.md` - [ ] Add `changelog.d/.keep` to seed the fragment directory - [ ] (Optional) Backfill retro-fragments for v1.0.0's substantive content as a one-off - [ ] Add `CHANGELOG.md` skeleton with `## [Unreleased]` section + `## [v1.0.0]` for the already-cut release - [ ] Add consumer workflow `.forgejo/workflows/release.yml` referencing `_release-prep.yml@vX.Y.Z` - [ ] Add consumer workflow `.forgejo/workflows/release-draft.yml` referencing `_release-draft.yml@vX.Y.Z` - [ ] Add consumer workflow `.forgejo/workflows/release-publish.yml` referencing `_release-publish.yml@vX.Y.Z` - [ ] Add consumer workflow `.forgejo/workflows/manifest-check.yml` referencing `_manifest-check.yml@vX.Y.Z` for PR CI - [ ] Document fragment + conventional-commits convention in `cellblock/CLAUDE.md` for chamber authors - [ ] Cut v1.0.1 (or v1.1.0) using the toolkit as the first end-to-end validation - [ ] Close #157 (manifest-vs-tag CI check) — this issue's `manifest-check.yml` adoption IS the resolution ## Open questions - Do we backfill v1.0.0's CHANGELOG section retroactively, or start from v1.0.1 cleanly? (Operator preference TBD; either works.) - Does cellblock want conventional-commits adoption ALSO (Shipwright's chamber-author shape) or just fragments-for-rich-prose? Both are supported by the toolkit. — QM, 2026-06-24, per Bosun ratification 13b1.

quartermaster referenced this issue from frankenbit/release-toolkit

2026-06-24 15:38:14 +02:00

v0.1 — initial cut: release-cut + CHANGELOG fragments + conventional-commits + manifest-vs-tag CI #1

2026-06-24 15:58:47 +02:00

v0.2.0 — runs-on parameterization + fragment newline normalization #3

2026-06-24 16:03:45 +02:00

fix: runs_on parameterization + defensive newline normalization (v0.2.0 slices 1+2) #5

2026-06-24 16:26:43 +02:00

feat(workflows): toolkit's own consumer workflows for v0.2.1+ dogfood (v0.2.0 slice 3) #6

quartermaster referenced this issue from a commit

2026-06-26 22:24:38 +02:00

chore: adopt release-toolkit @v0.10.1-rc.1 (closes #162; supersedes #167)