-
Notifications
You must be signed in to change notification settings - Fork 1
chore: Cherry-picked changes from upstream #123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Our direct dependency on `@actions/exec` was removed in 274ad334e, though we still depend on it indirectly.
We have this dependency anyway (since we're running on Node). This drops the problematic libsodium dependency so that the Action works on targets which libsodium doesn't support. Resolves: #56
The constant variables `cur_dev` and `min_dev` were added but never used in the comparison. This change is assuming this was by mistake. Otherwise `cur_dev` and `min_dev` are unused and should be removed.
Previously it was referencing the wrong group index (off by one), which is easy to do when relying on indices. Using capture groups here should make it less error prone (and also fixes this initial problem). Long term a small unit test should avoid this happening / regressing.
|
🚀 PR Updated! The PR has been updated with the latest cherry-picked commits. @step-security/maintained-actions-dev Please review and approve the changes. 📦 Target Release Version:
|
🔍 Cherry-Pick Verification Report📦 Upstream Changes: 📋 File-by-File Analysis:
|
🔍 Cherry-Pick Verification Report📦 Upstream Changes: 📋 File-by-File Analysis:
|
🔍 Cherry-Pick Verification Report📦 Upstream Changes: 📋 File-by-File Analysis:
|
Cherry-picked changes from upstream.