fix: enforce GDAM publication contract for v0.0.3 - #15
Merged
Merged
Conversation
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.
Tracks aviorstudio/fieldsofrevik#165 (do not close until production verification).
Remove undeclared publish.version, retain and pin valid install.version, select exact tested ZIP among multiple release assets, and verify the installed GDAM executable SHA-256. Add immutable upstream metadata/script fixtures and a structural workflow gate with negative/restored controls plus credential-free exact-tag/legacy/unknown CLI stub tests. Canonical CI/release gates run this before existing package/native/Web tests. Prepare approved patch v0.0.3; no Supabase API/session changes.
Local verification: npm ci; npm run test:publish (4 passing); npm audit (zero); external unsupported-version mutation fails and restored workflow passes; Python package build/verify; node --check; bash -n; git diff --check. Existing full package/native/Web suite remains required in exact-head CI. Release and fresh registry verification follow merge; v0.0.2 will not be overwritten.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.