Skip to content

Conversation

@Jamie-BitFlight
Copy link
Contributor

@Jamie-BitFlight Jamie-BitFlight commented Nov 23, 2025

GitHub Actions Version Updates

Summary by CodeRabbit

  • Chores
    • Updated CI/CD workflows to use newer action versions (checkout, Node setup, coverage reporting, and stale management).
    • No functional or behavioral changes to workflow logic; CI behavior should remain unchanged.

✏️ Tip: You can customize this high-level summary in your review settings.

@Jamie-BitFlight Jamie-BitFlight added automated dependencies Update one or more dependencies version labels Nov 23, 2025
@coderabbitai
Copy link

coderabbitai bot commented Nov 23, 2025

Walkthrough

Multiple GitHub Actions workflow files updated to bump action versions: actions/checkout -> v6.0.1, actions/setup-node -> v6.1.0 in some workflows, plus small version bumps for vitest-coverage-report and actions/stale. No other workflow logic changes.

Changes

Cohort / File(s) Summary
Deploy workflow
.github/workflows/deploy.yml
actions/checkout bumped v5.0.0v6.0.1; actions/setup-node bumped v6.0.0v6.1.0. No other changes.
Version updater workflow
.github/workflows/github_actions_version_updater.yml
actions/checkout bumped v5.0.0v6.0.1. No other changes.
Integration test workflow
.github/workflows/integration-test.yml
Bumped actions/checkout (both checkouts) v5.0.0v6.0.1 and actions/setup-node v6.0.0v6.1.0. No other changes.
Push linting workflow
.github/workflows/push_code_linting.yml
actions/checkout bumped v5.0.0v6.0.1. No other changes.
Test workflow
.github/workflows/test.yml
actions/checkout bumped v5.0.0v6.0.1; davelosert/vitest-coverage-report-action bumped v2.8.3v2.9.0. No other changes.
Stale workflow
.github/workflows/stale.yml
actions/stale bumped v10.1.0v10.1.1. No other changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Review focuses on CI semantics and compatibility of new action versions.
  • Pay extra attention to:
    • Workflows that also bump actions/setup-node (deploy.yml, integration-test.yml) for Node-version handling or inputs that may have changed.
    • test.yml for the vitest coverage action bump and any output/coverage artifact behavior.
    • Any workflow-specific uses of checkout features (submodules, fetch-depth, path) that could be impacted by checkout v6 behavior.

Possibly related PRs

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'fix(deps): update github action versions' directly and concisely describes the main change—bumping multiple GitHub Actions workflow dependencies across several workflow files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch github-actions-updates

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

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

@github-actions
Copy link
Contributor

github-actions bot commented Nov 23, 2025

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 49.81% 402 / 807
🔵 Statements 50.48% 414 / 820
🔵 Functions 65.74% 71 / 108
🔵 Branches 49.38% 200 / 405
File CoverageNo changed files found.
Generated in workflow #273 for commit 309960a by the Vitest Coverage Report Action

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 85ae8f0 and 309960a.

📒 Files selected for processing (6)
  • .github/workflows/deploy.yml (2 hunks)
  • .github/workflows/github_actions_version_updater.yml (1 hunks)
  • .github/workflows/integration-test.yml (2 hunks)
  • .github/workflows/push_code_linting.yml (1 hunks)
  • .github/workflows/stale.yml (1 hunks)
  • .github/workflows/test.yml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • .github/workflows/github_actions_version_updater.yml
  • .github/workflows/deploy.yml
  • .github/workflows/integration-test.yml
🔇 Additional comments (3)
.github/workflows/push_code_linting.yml (1)

35-35: The actions/checkout@v6.0.1 upgrade is compatible with this workflow.

The major version bump includes breaking changes to credential persistence (credentials now written to $RUNNER_TEMP instead of .git/config), but this workflow is unaffected. The custom ./.github/actions/setup-node action does not directly access git credentials from git config and operates in the standard workspace directory. The workflow runs on ubuntu-latest, which provides a runner version recent enough (v2.329.0+) to support v6's credential handling. No additional testing is required for this specific change.

.github/workflows/test.yml (2)

38-40: No action needed on actions/checkout@v6.0.1.

The major version bump from v5 to v6 does not introduce breaking changes to the ref parameter. The v6 documentation explicitly supports the ref: ${{ github.head_ref || github.ref }} pattern used at line 40, which is the recommended approach for PR workflows. The action accepts branch names, tag names, and full commit SHAs—all unchanged from v5.


60-60: v2.9.0 release is verified and safe to use. The release exists (published 2025-11-30) with backward-compatible bug fixes and new features. The changelog includes security updates, dependency bumps, Node.js version upgrade (20 → 24), new threshold-icons option, and file comparison features. The json-summary-path and json-final-path parameters remain compatible—no breaking changes or input modifications were introduced in this minor version update.

runs-on: ubuntu-latest
steps:
- uses: actions/stale@v10.1.0
- uses: actions/stale@v10.1.1
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

actions/stale v10.1.1 GitHub release

💡 Result:

I couldn't find a v10.1.1 release for actions/stale. The latest published release on the repository is v10.1.0 (see Releases). [1][2]

Sources:

  • actions/stale releases page. [1]
  • actions/stale repository README. [2]

Revert actions/stale version to v10.1.0 — v10.1.1 does not exist.

The version v10.1.1 has not been released. The latest published release is v10.1.0. Update the action reference to use actions/stale@v10.1.0 to ensure the workflow functions correctly.

🤖 Prompt for AI Agents
.github/workflows/stale.yml around line 15: the workflow references
actions/stale@v10.1.1 which does not exist; change the action reference to
actions/stale@v10.1.0 to match the latest published release so the workflow runs
correctly.

@Jamie-BitFlight Jamie-BitFlight merged commit f1bdab5 into main Dec 7, 2025
9 of 10 checks passed
@Jamie-BitFlight Jamie-BitFlight deleted the github-actions-updates branch December 7, 2025 01:56
Jamie-BitFlight pushed a commit that referenced this pull request Dec 7, 2025
## [1.8.5](v1.8.4...v1.8.5) (2025-12-07)

### Bug Fixes

* **deps:** update github action versions ([#420](#420)) ([f1bdab5](f1bdab5))
@Jamie-BitFlight
Copy link
Contributor Author

🎉 This PR is included in version 1.8.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

@Jamie-BitFlight Jamie-BitFlight added the released This issue/pull request has been released. label Dec 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated dependencies Update one or more dependencies version released This issue/pull request has been released.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants