Uh oh!
There was an error while loading. Please reload this page.
INFL-21383: chore: clear the Node 20 warnings on the ECR build job - #86
Conversation
Deploy runs annotate every "Build & Push ECR Docker Image" job with: Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f6, aws-actions/configure-aws-credentials@ff717079 Both come from this workflow: - configure-aws-credentials v4 is node20 -> v6.2.1, which is node24. That exact pin already runs on master in frontend-s3-managed.yaml. - actions/cache@0400d5f6 is not a step here at all; it is nested inside aquasecurity/trivy-action at the old pin, which calls actions/cache v4.2.4 internally. trivy-action v0.36.0 pins actions/cache v5.0.5. The step keeps `version: 'v0.69.2'`, so the Trivy scanner itself is unchanged - only the action wrapper moves. Input surfaces of both actions are identical between old and new; no inputs were added, removed or renamed. Scope is deliberately limited to the two lines that cause the annotation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A7RuYKDvUftG8c3AiWbZD3
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: infralight/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
Included review availability: 1 review is currently available. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. 📜 Recent review details🔇 Additional comments (1)
📝 WalkthroughWalkthroughThe workflow updates the AWS credentials action to v6.2.1 and the Trivy action to v0.36.0. Existing credentials and scan conditions remain unchanged. ChangesWorkflow action updates
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk:⚪ Minimal · up to This localized workflow maintenance updates action pins to remove Node 20 warnings without changing the scanner version or intended job behavior; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Your free Security trial is over. An organization admin can activate billing to continue. Comment |
| - name: Configure AWS Credentials | ||
| uses: aws-actions/configure-aws-credentials@ff717079ee2060e4bcee96c4779b553acc87447c # v4 | ||
| uses: aws-actions/configure-aws-credentials@254c19bd240aabef8777f48595e9d2d7b972184b # v6.2.1 |
There was a problem hiding this comment.
why do we need to update major version in this step?
There was a problem hiding this comment.
v5 doesn't clear the warning — it's still node20. v6 is the minimum bump that does:
| tag | runs.using |
|---|---|
| v4 | node20 ← the deprecated one |
| v5 | node20 |
| v6 | node24 |
And v6.0.0's only breaking change is exactly the thing we're after:
⚠ BREAKING CHANGES — Update action to use node24 (#1632)
Nothing this step passes is affected. v5.0.0's single breaking change was "changes invalid boolean input behavior", and this step passes no booleans — only role-to-assume, role-session-name and aws-region. The input surface from v4 to v6 is purely additive: 12 inputs added, none removed or renamed.
254c19bd (v6.2.1) is also the exact pin already running on master in frontend-s3-managed.yaml, so it's proven against the same OIDC assume-role pattern in this org.
| - name: Run Trivy Vulnerability Scanner | ||
| if: ${{ inputs.trivy-scan && inputs.environment == 'dev' }} | ||
| uses: aquasecurity/trivy-action@97e0b3872f55f89b95b2f65b3dbab56962816478 # master (v0.69.2) | ||
| uses: aquasecurity/trivy-action@ed142fd0673e97e23eac54620cfb913e5ce36c25 # v0.36.0 |
There was a problem hiding this comment.
why version downgrade? please use 0.69.2
Uh oh!
There was an error while loading. Please reload this page.
Two lines. Clears the Node 20 deprecation annotation on every
Build & Push ECR Docker Imagejob, e.g. run 32721041959:configure-aws-credentialsv4 (node20) → v6.2.1 (node24). That exact pin already runs on master infrontend-s3-managed.yaml.actions/cache@0400d5f6isn't a step in this workflow — it's nested insideaquasecurity/trivy-actionat the old pin, which callsactions/cachev4.2.4 internally. v0.36.0 pinsactions/cachev5.0.5. The step keepsversion: 'v0.69.2', so the Trivy scanner itself does not change — only the action wrapper.Input surfaces of both actions are identical between old and new pins; nothing added, removed or renamed. Both new pins verified to resolve to real commits.
The app-server half of this annotation is already on main (app-server#3003).
Testing. Reusable workflows can't be exercised from a branch — callers reference
@master— so this is static review plus the prior art above. To execute it before merge, point a caller at this branch and dispatch a dev deploy:Scope is deliberately limited to the annotation. The broader Node 24 / pinning / permissions work is parked in #85.
No.
🤖 Generated with Claude Code
https://claude.ai/code/session_01A7RuYKDvUftG8c3AiWbZD3
Summary by CodeRabbit