Repository navigation
Reconcile Frontend 1.0.0 release metadata with the post-tag source revision #24
Description
Context
Both current Frontend Component Release Metadata documents in the Registry Catalog identify package version 1.0.0:
registry/releases/frontend-tui-1.0.0.jsonregistry/releases/frontend-gui-sdl-1.0.0.json
Both pin source revision 1373715c23eb965445caa926de3a99d9c0246f81.
The official GitHub release/tag v1.0.0 points to commit 8f919b10a17453187f13d826dcd1348dc4e2bcaa, published on 2026-11-04. Comparing the source revision with that tag shows the Catalog source is 159 commits ahead. The current CMake project version remains 1.0.0, while the Changelog contains changes after the release tag.
This may be an intentional rolling source snapshot for the same package version, but it needs an explicit release/version decision. The Registry Catalog uses immutable metadata URIs and digests; do not retarget the existing metadata documents in place.
Acceptance
- Decide that the post-1.0.0 source is a new patch package identity: Frontend
1.0.1is the Registry integration candidate. The existing1.0.0release metadata remains immutable. - If it is a new package version, bump CMake/package metadata and publish the appropriate tag/release only after the relevant release gates pass.
- Publish new immutable Release Metadata documents for the changed package identity/source revision; never overwrite the current metadata identity. TUI and GUI-SDL 1.0.1 records were added by merged Frontend PR release(frontend): prepare immutable 1.0.1 integration candidate #34 with source revision and exact SHA-256 values.
- Update the Registry Catalog Index to reference both new metadata URIs and exact SHA-256 digests. Merged Registry PR release: publish Core, TUI and GUI-SDL packages as explicit variants #40 at Catalog commit
2a611eca830c0f235dacab04a1d006a8fd46e586; previous 1.0.0 entries were retained. - Confirm CDIN's pinned Registry commit selects the intended TUI and GUI-SDL source revisions and that the full cross-platform product matrix passes. CDIN pins Catalog
2a611eca830c0f235dacab04a1d006a8fd46e586; TUI and GUI-SDL 1.0.1 both passed on Linux/macOS/Windows in CDIN run 42447891569. - Keep the GUI-SDL production gates and Protocol issue fix(session): support detach and reattach role transitions #14 linked; this issue is about release identity, not a claim that GUI-SDL presentation is complete. Frontend Complete remaining GUI-SDL production and release gates #15 and Spec fix(session): support detach and reattach role transitions #14 remain open for renderer, Unicode and IME acceptance.
This is a release-metadata reconciliation task. It does not authorize a new release/tag before the release owner confirms the version decision.
Activity
m-mdy-m commentedon Nov 8, 2026
The post-tag source has moved further: Frontend PRs #29 and #30 are now merged, and #31's design proposal is merged. These are new commits after both the
v1.0.0tag and the existing immutable Registry source snapshot. I am preserving the current metadata URI/digest rather than retargeting it. A package-version decision is still needed before publishing a new metadata identity; the likely safe direction is a new patch package version if the release workflow and component API review confirm only compatible changes.m-mdy-m commentedon Nov 8, 2026
Decision and implementation are now in progress: the merged PR #34 bumps CMake/Foundation package identity to 1.0.1, fixes tag-derived archive version selection, and adds separate immutable TUI/GUI-SDL 1.0.1 metadata. The 1.0.0 documents and source pins remain unchanged. The exact-head frontend matrix passed before merge. I am not closing #24 yet: Registry Catalog must add both new metadata URI+digest entries and CDIN must pin the new Registry revision and pass its exact product matrix before we can call the cross-repository identity synchronized. This remains an integration candidate, not a formal v1.0.1 tag/release.
m-mdy-m commentedon Nov 8, 2026
The cross-repository acceptance is now complete: Frontend PR #34 (CMake/Foundation 1.0.1 package identity and immutable TUI/GUI-SDL metadata), Registry PR #40 (Catalog entries + exact metadata digests), and CDIN PR #114 (Registry pin + both Product Definitions) are merged. Exact CDIN run 42447891569 passed all six Linux/macOS/Windows × TUI/GUI-SDL jobs plus the full-stack ASan/UBSan/leak job; resolver selected both Frontend variants at 1.0.1 and startup/runtime smoke passed. The remaining acceptance item is the formal
v1.0.1tag/GitHub Release. It has not been created: the current candidate is integrated and tested, but the GUI-SDL renderer/IME/product gates remain separately tracked in #15 / Spec #14, and the GitHub connection available here does not expose a tag/release-creation action. I am leaving #24 open rather than claiming a formal release that does not exist.m-mdy-m commentedon Nov 8, 2026
Release identity status (2026-11-08)
The current
mainhas moved beyond the historical 1.0.1 candidate: immutable TUI and GUI-SDL 1.0.2 Release Metadata documents are committed, and the Registry Catalog points at those documents. The CDIN cross-platform matrix has verified those pinned source candidates.The formal
v1.0.2package tag/Release has not been published. That is intentional: the GUI-SDL production gates in #15 remain open, so the candidate must not be promoted to a supported release yet. Keep the 1.0.0 metadata immutable and keep this issue open until release identity, package version and the applicable product gates are reconciled.m-mdy-m commentedon Nov 8, 2026
Release identity update — 2026-11-09
The current Frontend main and Registry Catalog have advanced beyond the historical 1.0.1 candidate to immutable 1.0.2 TUI/GUI-SDL Release Metadata. However, the formal v1.0.2 package tag/GitHub Release has not been published. The current public release listing still shows v1.0.0 with a source archive only.
The 1.0.2 metadata identity is therefore an integrated candidate, not a published package release. Keep this issue open until the formal package version/release decision and release assets are reconciled; do not overwrite the immutable 1.0.0/1.0.1 metadata identities or imply that GUI-SDL is production-ready.