Open
Conversation
🔐 Commit Signature Verification✅ All 1 commit(s) passed verification
Summary
Required key type: Last verified: 2026-03-12 05:29 UTC |
mpastecki
approved these changes
Mar 16, 2026
Contributor
mpastecki
left a comment
mpastecki
left a comment
There was a problem hiding this comment.
Reviewed: SHA 9565281eda0731b1d20c4025c43339fb0a23812e verified against current tibdex/backport v2 tag. Permissions correctly scoped to minimum required (contents: write, pull-requests: write). LGTM.
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
2 participants
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.
Pinned action to commit SHA — tibdex/backport@9565281 # v2. A compromised or force-pushed v2 tag can no longer substitute malicious code; the runner will only execute the exact commit that was audited.
Restricted permissions — added an explicit block with only contents: write (to push the backport branch) and pull-requests: write (to open the PR and post comments). All other permissions (actions, id-token, packages, etc.) default to none, limiting blast radius if the action is ever abused.