Align stable Action guidance with v0.5.3 - #54
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.
Summary
d5fe3da78400a1b4d4154c0ddd9b84c3ef662e06Why
v0.5.3 is already a public GitHub release, but the repository still told users to install
@v0.5.2and the main-branch published-Action smoke continued validating v0.5.2. That leaves the newest public Action outside the permanent post-release smoke gate and makes current integration guidance stale.The v0.5.3 annotated tag resolves to release commit
d5fe3da78400a1b4d4154c0ddd9b84c3ef662e06, so the security-sensitive full-SHA example now points to the same release as the stable tag guidance.Verification
npm testpassed after the documentation changeshzw0813/proofdiff@v0.5.3directly