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
• xt0rted/markdownlint-problem-matcher published a new release v3.0.0 on 2024-02-24T23:41:19Z
• actions/checkout published a new release v4.2.2 on 2024-10-23T14:46:00Z
• pozil/auto-assign-issue published a new release v2.2.0 on 2025-02-04T09:57:00Z
• davelosert/vitest-coverage-report-action published a new release v2.8.1 on 2025-04-06T06:58:50Z

Summary by CodeRabbit

• Chores
  • Updated versions of several GitHub Actions across workflows for issue assignment, deployment, code linting, and testing to improve reliability and compatibility.
  • Upgraded actions include checkout, auto-assign-issue, markdownlint-problem-matcher, reviewdog/action-eslint, and vitest-coverage-report-action. No changes to workflow logic or user-facing features.

[coderabbitai]

Walkthrough

The updates modify several GitHub Actions workflow files to use newer versions of third-party actions. The changes include upgrading the versions of actions such as actions/checkout, pozil/auto-assign-issue, xt0rted/markdownlint-problem-matcher, reviewdog/action-eslint, and davelosert/vitest-coverage-report-action. No changes were made to workflow logic, environment variables, or control flow; only the versions of the actions referenced in the workflows were updated.

Changes

File(s)	Change Summary
.github/workflows/assign.yml	Updated pozil/auto-assign-issue action from v1.13.0 to v2.2.0.
.github/workflows/deploy.yml	Updated actions/checkout action from v4.1.1 to v4.2.2 in the deploy job.
.github/workflows/github_actions_version_updater.yml	Updated actions/checkout action from v4 to v4.2.2 in the version updater workflow.
.github/workflows/push_code_linting.yml	Updated actions/checkout from v4.1.1 to v4.2.2, xt0rted/markdownlint-problem-matcher 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.1.

Sequence Diagram(s)

No sequence diagram is generated as the changes are limited to action version updates and do not affect workflow logic or control flow.

---

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 generate sequence diagram to generate a sequence diagram of the changes in 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 #134 for commit cd3cfd3 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.
Line 40 has trailing whitespace, which can cause linter warnings. Please trim the extra spaces.

🧰 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 cd3cfd3.

📒 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: Verify compatibility with major version bump for auto-assign action.
Moving from v1.x to v2.x may introduce breaking changes in inputs or behavior. Please confirm that pozil/[email protected] works as expected with your current configuration.

.github/workflows/github_actions_version_updater.yml (1)

14-14: Upgrade actions/checkout to patch version 4.2.2.
This patch release aligns with other workflows and includes minor fixes. No breaking changes expected.

.github/workflows/deploy.yml (1)

55-55: Standardize actions/checkout version to 4.2.2.
Patch bump is consistent with other workflows and is backward-compatible.

.github/workflows/test.yml (2)

34-34: Update actions/checkout to v4.2.2.
This patch upgrade matches other CI workflows and is backward-compatible.

---

54-54: Upgrade vitest-coverage-report-action to v2.8.1.
Pinning to the latest patch version ensures the most recent bug fixes without API changes.

.github/workflows/push_code_linting.yml (3)

35-35: Sync actions/checkout version to v4.2.2.
Consistent with other workflows and safe as a patch release.

---

43-43: Verify major version bump for markdownlint-problem-matcher.
The update from v2 to v3.0.0 likely includes breaking changes. Confirm that any input names or behavior changes are addressed.

---

47-47: Upgrade action-eslint to v1.33.2.
Minor version bump is backward-compatible and includes new ESLint rule support.