Update GitHub Action Versions

[Jamie-BitFlight]

GitHub Actions Version Updates

• pozil/auto-assign-issue published a new release v2.2.0 on 2025-02-04T09:57:00Z
• reviewdog/action-eslint published a new release v1.33.2 on 2025-03-18T07:08:17Z
• actions/checkout published a new release v4.2.2 on 2024-10-23T14:46:00Z
• xt0rted/markdownlint-problem-matcher published a new release v3.0.0 on 2024-02-24T23:41:19Z
• davelosert/vitest-coverage-report-action published a new release v2.8.3 on 2025-05-19T05:02:37Z

Summary by CodeRabbit

• Chores
  • Updated various GitHub Actions workflows to use newer versions of actions for improved reliability and security. No changes to workflow logic or user-facing features.

[coderabbitai]

Walkthrough

This update revises several GitHub Actions workflow files to use newer versions of existing actions. The changes are limited to updating version tags for actions such as actions/checkout, pozil/auto-assign-issue, davelosert/vitest-coverage-report-action, github/super-linter, and related linting and assignment tools. No workflow logic or control flow was altered.

Changes

Files	Change Summary
.github/workflows/assign.yml	Updated pozil/auto-assign-issue action from v1.13.0 to v2.2.0.
.github/workflows/deploy.yml .github/workflows/github_actions_version_updater.yml	Updated actions/checkout action from v4.1.1/v4 to v4.2.2.
.github/workflows/push_code_linting.yml	Updated actions/checkout from v4.1.1 to v4.2.2, github/super-linter from v2 to v3.0.0, and reviewdog/action-eslint from v1.20.0 to v1.33.2.
.github/workflows/test.yml	Updated actions/checkout from v4.1.1 to v4.2.2 and davelosert/vitest-coverage-report-action from v2 to v2.8.3.

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch gh-actions-update-1751159471

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	72.11%	2092 / 2901
🔵	Statements	72.11%	2092 / 2901
🔵	Functions	76.13%	67 / 88
🔵	Branches	82.96%	190 / 229

File Coverage

No changed files found.

Generated in workflow #143 for commit 91ed543 by the Vitest Coverage Report Action

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/push_code_linting.yml (1)

40-40: Remove trailing whitespace to satisfy yamllint.

-      - name: Install Deps␠
+      - name: Install Deps

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f822bc2 and 91ed543.

📒 Files selected for processing (5)

• .github/workflows/assign.yml (1 hunks)
• .github/workflows/deploy.yml (1 hunks)
• .github/workflows/github_actions_version_updater.yml (1 hunks)
• .github/workflows/push_code_linting.yml (1 hunks)
• .github/workflows/test.yml (2 hunks)

🧰 Additional context used

🪛 YAMLlint (1.37.1)

.github/workflows/push_code_linting.yml

[error] 40-40: trailing spaces

(trailing-spaces)

🔇 Additional comments (8)

.github/workflows/assign.yml (1)

9-13: Confirm compatibility after major-version bump of auto-assign-issue.

pozil/auto-assign-issue jumped from the v1 series to v2.2.0. Despite similar defaults, v2 renamed/removed a few inputs (e.g., repo-token → github-token). Please double-check that:

1. repo-token is still an accepted input name in v2.
2. No new required permissions or scopes are needed.

If everything still works in dry-runs, no further action is required.

.github/workflows/deploy.yml (1)

55-58: Checkout bump looks safe.

actions/[email protected] is a minor update over v4.1.1; there are no breaking-change notes. Good to keep the fleet consistent.

.github/workflows/github_actions_version_updater.yml (1)

14-18: LGTM – keep all jobs on the same checkout patch level.
No behavioural change expected.

.github/workflows/push_code_linting.yml (3)

35-36: Checkout version bump is fine.
Nothing further.

---

43-45: Major upgrade of markdownlint-problem-matcher – re-verify matcher keys.

xt0rted/markdownlint-problem-matcher@v3 tweaked the matcher JSON; if the workflow depends on custom problem-matcher names, run a quick PR test to ensure annotations still surface.

---

47-52: ESLint reviewdog bump looks harmless.
Patch-level upgrade within v1, no API changes flagged.

.github/workflows/test.yml (2)

34-37: Checkout patch bump approved.

---

54-57: Ensure new vitest-coverage-report-action version still finds the JSON paths.

v2.8.3 introduces stricter default globbing; confirm that
./out/coverage-summary.json and ./out/coverage-final.json are still discovered (path is relative to $GITHUB_WORKSPACE).