OSCER-457: Upgrade github checkout action to v6

[jdettmannnava]

Ticket

Resolves OSCER-457

Changes

All github workflows upgraded the checkout action from v4 to v6.
e2e workflow node upgraded to v6.

Context for reviewers

Wanting to keep using the latest versions as the default.

• checkout: https://github.com/marketplace/actions/checkout
  • v5 upgraded to node 24 (requires a minimum Actions Runner version of v2.327.1 to run.
  • v6 improved credential security:
• setup-node (https://github.com/marketplace/actions/setup-node-js-environment)
  • v5 upgraded to node 24 (requires a minimum Actions Runner version of v2.327.1 to run; adds caching
  • v6 has more caching rules, removes always-auth (we don't use)

Testing

Already using in oscer, and it works fine.

[coderabbitai]

Warning

Rate limit exceeded

@jdettmannnava has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 31 minutes and 28 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3ff2e8ee-28a1-4e7c-94eb-bac3184a2b27

📥 Commits

Reviewing files that changed from the base of the PR and between ad00fcf and 421df82.

📒 Files selected for processing (21)

• .github/workflows/build-and-publish.yml
• .github/workflows/check-ci-cd-auth.yml
• .github/workflows/check-infra-deploy-status.yml
• .github/workflows/ci-docs.yml
• .github/workflows/ci-e2e-static-checks.yml
• .github/workflows/ci-infra.yml
• .github/workflows/ci-{{app_name}}-infra-service.yml.jinja
• .github/workflows/database-migrations.yml
• .github/workflows/deploy.yml
• .github/workflows/e2e-tests.yml
• .github/workflows/pr-environment-checks.yml
• .github/workflows/pr-environment-destroy.yml
• .github/workflows/scan-orphaned-environments.yml
• .github/workflows/send-system-notification.yml
• .github/workflows/template-only-cd.yml
• .github/workflows/template-only-ci-app.yml
• .github/workflows/template-only-ci-infra.yml
• .github/workflows/template-only-cleanup-orphaned-infra-test-resources.yml
• .github/workflows/template-only-scan-orphaned-infra-test-resources.yml
• .github/workflows/vulnerability-scans.yml
• docs/infra/style-guide.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jdettmann/oscer-457-upgrade-actions-checkout

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}