Skip to content

fix: use Zig-issued release consumer fingerprint - #100

Merged
LukasNiessen merged 1 commit into
mainfrom
fix/49-release-consumer-fingerprint
Aug 24, 2026
Merged

LukasNiessen merged 1 commit into
mainfrom
fix/49-release-consumer-fingerprint

Conversation

@LukasNiessen

Copy link
Copy Markdown
Collaborator

Summary

  • replace the generated external consumer's arbitrary package fingerprint with the exact Zig 0.16 value reported by the failed release-candidate smoke test
  • pin that fingerprint in the release contract unit test

The first v0.0.1 tag workflow safely skipped publication: all platform/quality gates passed, the external consumer stopped before package fetch, and no draft or published release was created. The unpublished candidate tag was removed. This change is under scripts/, outside build.zig.zon.paths, so the reviewed ArchUnitZig package hash is unchanged.

Validation

  • python -B -m unittest scripts.test_install_zig scripts.test_release
  • python -B scripts/check_ci.py
  • python -B scripts/release.py validate
  • zig build test

Refs #49

@LukasNiessen

Copy link
Copy Markdown
Collaborator Author

Self-review complete: no findings. The change is limited to the fingerprint Zig emitted for the generated external-consumer package, with a regression assertion pinning that value. Hosted Debug checks passed on Linux, Windows, and macOS; ReleaseSafe, formatting, docs, and local release validation also passed.

@LukasNiessen
LukasNiessen merged commit 55a54a7 into main Aug 24, 2026
5 checks passed
@LukasNiessen
LukasNiessen deleted the fix/49-release-consumer-fingerprint branch August 24, 2026 16:01
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