Skip to content

Bump ruby/setup-ruby from 1 to 1.312.0 #449

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.

Sign up for GitHub

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

Closed
dependabot wants to merge 1 commit into from
Closed

Bump ruby/setup-ruby from 1 to 1.312.0 #449

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ jobs:
- uses: actions/checkout@v6

- name: Set up Ruby
uses: ruby/setup-ruby@v1
uses: ruby/setup-ruby@v1.312.0

@aikido-pr-checks aikido-pr-checks Bot Jun 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Workflow uses ruby/setup-ruby@v1.312.0 (tag) instead of an immutable SHA and lacks checksum verification; pin the action to a specific commit SHA and enable checksum verification where supported.

Details

✨ AI Reasoning
​The PR changed the workflow to use ruby/setup-ruby@v1.312.0 instead of ruby/setup-ruby@v1. This introduced a dependency reference that is still a version tag rather than an immutable commit SHA and does not include checksum verification. Using a tag allows the action source to change if the tag is repointed or re-released, which undermines strict dependency management. The change therefore fails the requirements to pin exact package versions (preferably SHAs) and to enable checksum verification where supported. This is a clear, actionable alignment issue with the dependency rules introduced/worsened by this commit.

🔧 How do I fix it?
Include lockfiles in your repo and CI. Pin exact versions or SHAs in manifests. Enable checksum verification. Set ignore-scripts in npm or equivalent. Enforce a 72hr minimum package age policy to avoid newly published malicious packages.

Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info

with:
bundler-cache: true

Expand Down
Loading