docs: align historical design docs with the latest tag removal - #36
Merged
Conversation
PR #34 removed the mutable :latest tag but deliberately left the docs/superpowers/ design records untouched to keep that PR reviewable. Those documents still describe a tagging scheme this repository no longer implements, so a reader could mistake them for current behaviour or run a command naming a tag that does not exist. Keep the historical record intact and add short, dated superseded notes wherever the tagging scheme is described: the minor line is the most permissive published tag, the point release is immutable, and there is deliberately no :latest because a rolling alias lets a consumer deploy an unpinned image and have it change underneath them with no signal. Update the one reader-facing command that named a tag which no longer exists (podman inspect of the exported image) to the local build tag, and flag the historical Containerfile snippet with the published tag to use instead. Closes #35 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #35
PR #34 removed the mutable
:latesttag but deliberately left thedocs/superpowers/design records untouched to keep that PR reviewable. They still describe a tagging scheme this repository no longer implements.What changed
These are historical records, so nothing that was decided in June 2026 has been rewritten. Instead, each place that describes the tagging scheme now carries a short, clearly-marked dated note pointing at current behaviour: the FSDK minor line is the most permissive published tag, the point release is immutable, and there is deliberately no
:latest(PR #34 / issue #23). The rationale is preserved in the notes: a rolling alias lets a consumer deploy an unpinned image and have it change underneath them with no signal, so every consumer must state how much drift it accepts.docs/superpowers/specs/2026-06-25-fsdk-containers-distroless-suite-design.md— notes on both Versioning sections and the CI manifest step.docs/superpowers/specs/2026-06-25-fsdk-point-release-bumper-design.md— note on the dynamic-tag calculation step.docs/superpowers/plans/2026-06-25-fsdk-containers-static-image.md— a doc-level superseded note, plus per-section notes on the global constraints, Task 3 (local build tag), Task 4 (tags/tag-push), theContainerfilesnippet, and the quoted README draft.Reader-facing commands were updated rather than annotated:
just exportverification step now inspectsghcr.io/projectbluefin/base:build(whatjust exportactually loads today) instead ofstatic:latest.Containerfilesnippet is flagged as not-runnable with the published equivalent (FROM ghcr.io/projectbluefin/base:25.08) given inline.Deliberately left as historical prose
Verbatim reproductions of files as they were written at the time — the June 2026 Justfile recipes, the
Containerfilebody, the quoted README draft, and theorg.opencontainers.image.ref.nameindex annotation (which is still what the liveelements/oci/*.bstemit) — keep their original:latesttext. Each is covered by a dated note in its section. Rewriting them would falsify the record.Validation
just validatepasses (element graph resolves)..pre-commit-config.yamlin this repo; no new tooling added.