fix: v0.33.5 — stale Dockerfile OCI labels, README gaps, CHANGELOG backfill - #44
Merged
Conversation
…, CHANGELOG backfill Fixes #43: - Dockerfile custom io.x-fusa.* labels were hardcoded (spec-version stuck at "1.9", four versions behind fusa.SpecVersion's actual 1.10.12; image version stuck at "0.25.1"). Both are now ARG-driven (VERSION, SPEC_VERSION) with current-value defaults for local `docker build`. docker-publish.yml now derives SPEC_VERSION by grepping fusa.go's SpecVersion constant and VERSION from the pushed tag, passing both via --build-arg, so these labels track the source of truth automatically instead of going stale again. (org.opencontainers.image.version was already corrected at publish time by docker/metadata-action, so only local builds and the raw Dockerfile value were actually affected.) - README.md's cmd/gofusa package-table row was missing 9 subcommands: hara, iso26262, iec61508, disposition, impact, metrics, misra, capabilities, version. Added all 9 to the row (43 total). capabilities and version had zero README mentions anywhere, so also added Quick Start examples for both. - CHANGELOG.md was missing entries for 5 tagged/released versions: v0.29.1, v0.25.1, v0.25.0, v0.24.0, v0.8.0. Backfilled each in its correct chronological slot with content derived from `git log` and `gh release view`. (v0.8.0 shares its commit with v0.9.0 — a squash merge that tagged both at once — noted inline; no new GitHub release created for it, per the pre-automation-tag scope boundary.) Bumped Version to 0.33.5 (fusa.go, README.md, docs/tool-safety-manual.md) to satisfy the "Doc version check" CI gate. Signed-off-by: SoundMatt <SoundMatt@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 #43
Summary
io.x-fusa.*OCI labels were hardcoded and stale (spec-version="1.9"vs. the actualfusa.SpecVersionof1.10.12;org.opencontainers.image.version="0.25.1"). Both are now injected viaARG VERSION/ARG SPEC_VERSION, with.github/workflows/docker-publish.ymlderiving them at build time (spec version grepped fromfusa.go, version from the pushed tag) and passing them via--build-arg, so they can't go stale again. Localdocker buildstill gets sane current-value defaults.cmd/gofusapackage-table row was missing 9 subcommands (hara,iso26262,iec61508,disposition,impact,metrics,misra,capabilities,version) — added all 9.capabilitiesandversionhad no README mentions at all, so Quick Start examples were added for both.v0.29.1,v0.25.1,v0.25.0,v0.24.0,v0.8.0) — backfilled each in its correct chronological slot usinggit log/gh release viewdata. Per the issue's explicit scope boundary, no new GitHub release was created forv0.8.0(it shares a commit withv0.9.0and predates the release-automation workflow).Versionto0.33.5(fusa.go, README.md, docs/tool-safety-manual.md) to satisfy the "Doc version check" CI gate, and added the v0.33.5 CHANGELOG entry.Test plan
go build ./...go test ./...— all packages pass, zero regressionsgofmt -l ./go vet ./...— clean./gofusa check --dir .— 0 errors (same baseline warning count as before)