ci(release): publish verified Windows artifacts - #21
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
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.
Release contract PR
Scope
Adds a tag-only Windows GitHub Release workflow and artifact-side release identity. The tracked source manifest remains explicitly
unreleased; only a verified bundled runtime identity makes an installed product reportreleasedandpublic_installer=available.Controls
origin/mainSHA.Local evidence
tests/test_release_manifest.py: 14 passedgit diff --check: passedRisk and rollback
The workflow is tag-only and does not modify the existing required CI workflow. Rollback is to remove the release tag/release and revert this commit; no user runtime data is changed by the workflow before the installer lifecycle test, which performs uninstall cleanup.