Skip to content

fix(release): sync extension evidence after asset inputs#65

Merged
f0rr0 merged 1 commit into
mainfrom
f0rr0/fix-release-evidence-sync
Jun 19, 2026
Merged

fix(release): sync extension evidence after asset inputs#65
f0rr0 merged 1 commit into
mainfrom
f0rr0/fix-release-evidence-sync

Conversation

@f0rr0

@f0rr0 f0rr0 commented Jun 19, 2026

Copy link
Copy Markdown
Owner

Summary

  • Refresh extension evidence after release sync updates the WASIX asset input fingerprint.
  • Commit the regenerated transitional evidence digest and generated evidence table for the current main release state.
  • Keep future generated release PRs from breaking extension-native lanes after release-derived asset inputs change.

Validation

  • python3 src/extensions/tools/check-extension-model.py --check
  • tools/release/sync_release_pr.py --check
  • tools/release/release.py check
  • bun tools/policy/assertions/assert-source-inputs.mjs extensions
  • python3 -m py_compile tools/release/sync_release_pr.py src/extensions/tools/check-extension-model.py
  • git diff --check

@f0rr0 f0rr0 merged commit 38c6a21 into main Jun 19, 2026
0 of 2 checks passed
@f0rr0 f0rr0 deleted the f0rr0/fix-release-evidence-sync branch June 19, 2026 20:46
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