Update GitHub Action Versions

[Jamie-BitFlight]

GitHub Actions Version Updates

• 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.0 on 2024-11-17T09:32:19Z
• pozil/auto-assign-issue published a new release v2.2.0 on 2025-02-04T09:57:00Z

Summary by CodeRabbit

• Chores
  • Upgraded various CI workflow dependencies to their latest stable versions.
  • Enhanced the automation for issue assignment, code checkout, linting, and test coverage reporting to improve performance and reliability.

[coderabbitai]

Walkthrough

This pull request updates several GitHub Actions workflow files to use newer versions of various actions. The auto-assignment workflow now uses pozil/[email protected]. Multiple workflows have their actions/checkout version upgraded to v4.2.2, and additional dependencies in the linting and testing workflows are updated as well. The overall workflow behavior and triggering conditions remain unchanged.

Changes

File(s)	Change Summary
…/assign.yml	Updated pozil/auto-assign-issue from v1.13.0 to v2.2.0.
…/deploy.yml, …/github_actions_version_updater.yml	Updated actions/checkout to v4.2.2 (from v4.1.1 or v4 respectively).
…/push_code_linting.yml	Updated actions/checkout to v4.2.2; updated xt0rted/markdownlint-problem-matcher from v2 to v3.0.0; updated reviewdog/action-eslint from v1.20.0 to v1.33.2.
…/test.yml	Updated actions/checkout to v4.2.2; updated davelosert/vitest-coverage-report-action from v2 to v2.8.0.

---

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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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 #131 for commit f18a4b0 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 Spaces
Static analysis has flagged trailing spaces on line 40. Please remove any unnecessary whitespace to adhere to YAML best practices.

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 40-40: trailing spaces

(trailing-spaces)

📜 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 f18a4b0.

📒 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.35.1)

.github/workflows/push_code_linting.yml

[error] 40-40: trailing spaces

(trailing-spaces)

🔇 Additional comments (8)

.github/workflows/assign.yml (1)

9-9: Auto-Assign Action Version Updated
The pozil/auto-assign-issue action has been updated to v2.2.0 as intended. The version bump aligns with our PR objectives and does not alter the existing parameters or filtering condition.

.github/workflows/deploy.yml (1)

55-55: Checkout Action Version Updated
The actions/checkout action is now set to v4.2.2, ensuring consistency with other workflow files and incorporating the latest improvements and fixes.

.github/workflows/github_actions_version_updater.yml (1)

14-14: Standardized Checkout Version in Updater Workflow
The update to actions/[email protected] helps keep the version consistent across all workflows. This change is clear and straightforward.

.github/workflows/test.yml (2)

34-34: Checkout Action Version Updated in Test Workflow
The checkout step now uses v4.2.2 of the actions/checkout action, aligning with our overall update approach.

---

54-54: Vitest Coverage Report Action Version Updated
The davelosert/vitest-coverage-report-action has been updated to v2.8.0, updating the coverage analysis tool to the latest supported version.

.github/workflows/push_code_linting.yml (3)

35-35: Checkout Action Version Consistency
The updated actions/[email protected] ensures the workflow follows the standardized version across the repository.

---

43-43: Markdownlint Action Version Updated
The xt0rted/markdownlint-problem-matcher action has been updated to v3.0.0, which brings enhancements and compatibility improvements for markdown linting.

---

47-47: ESLint Action Version Updated
The reviewdog/action-eslint action is now at v1.33.2, ensuring that our linting process uses the latest version with improved performance and bug fixes.