Skip to content

Pin v0.7 consumer checksums and fix temporary cache cleanup - #5

Merged
simpcl merged 2 commits into
mainfrom
dev
Oct 13, 2026
Merged

simpcl merged 2 commits into
mainfrom
dev

Conversation

@simpcl

@simpcl simpcl commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Published-dependency functional checks passed, but their cleanup failed on Linux because Go module directories are read-only. Make only the script-owned temporary tree writable before removal, retain the original verification failure status and return nonzero if cleanup itself fails. Signal exits retain their conventional status.

Validation: shell syntax and read-only-cache cleanup probes pass for success, failure and SIGTERM. Fresh-cache release verification is rerun against the published Community v0.7.0 tag. This changes verification infrastructure, not the released runtime or its designated API signatures.

Both local fresh-cache release gates now pass with the official Go module proxy: GOPROXY=https://proxy.golang.org make test-extension-consumer-release and the paired GOPROXY=https://proxy.golang.org ./scripts/verify-community release (Go 1.26.3). The published module origin is 3d04b7a0207a6d31746a1b196ae9d82097c2087c; module and go.mod checksums are pinned. Original verification exit status and cleanup success are checked separately.

@simpcl
simpcl merged commit ed3a26f into main Oct 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant