Fix Protection Off semantics and prepare v1.3.7 - #399
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
Prepare
v1.3.7with the already-merged transient release-download fix from #397 and correct the Protection mode regression tracked in #398.Changes
1.3.7from Fix transient release downloads and bump v1.3.7 #397502/503/504failuresmutation_execution_denied:authority_mode_offexecution denialhigh-assurance/ Sensitive actions andall/ Every GitHub write trusted-authority behavior unchanged1.3.7README / CHANGELOG release notesRegression coverage
The Protection-Off regressions prove that:
authorityMode=offwithout redeeming a Windows Hello grantexplicitInstructioncannot self-authorize the same pathThe initial execution regression used
create_issueand accidentally entangled the unrelated create-idempotency receipt verifier. The corrected test usesassign_issue, which still exercises a high-assurance GitHub write plus deterministic postcondition verification without introducing remote-create receipt semantics.Release boundary
This PR prepares the source for
v1.3.7. It does not authorize or perform a tag, GitHub Release, npm publication, merge, or other release publication.Fixes #398