Update GitHub Action Versions

[Jamie-BitFlight]

GitHub Actions Version Updates

• pozil/auto-assign-issue published a new release v2.0.0 on 2024-05-14T13:52:11Z
• xt0rted/markdownlint-problem-matcher published a new release v3.0.0 on 2024-02-24T23:41:19Z
• reviewdog/action-eslint published a new release v1.24.0 on 2024-04-22T12:08:16Z
• actions/checkout published a new release v4.1.6 on 2024-05-16T18:11:28Z
• davelosert/vitest-coverage-report-action published a new release v2.3.1 on 2024-04-12T09:35:50Z

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflows to use the latest versions of various actions, improving stability and performance.

[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 #87

[coderabbitai]

Walkthrough

This update primarily involves upgrading the versions of various GitHub Actions used across multiple workflow files. The changes aim to enhance functionality, improve performance, and ensure compatibility with the latest features and security improvements.

Changes

Files	Change Summary
.github/workflows/assign.yml	Upgraded pozil/auto-assign-issue from v1.13.0 to v2.0.0.
.github/workflows/deploy.yml	Updated actions/checkout from v4.1.1 to v4.1.6.
.github/workflows/github_actions_version_updater.yml	Updated actions/checkout from v4 to v4.1.6.
.github/workflows/push_code_linting.yml	Updated versions for multiple actions: actions/checkout from v4.1.1 to v4.1.6, xt0rted/markdownlint-problem-matcher from v2 to v3.0.0, and reviewdog/action-eslint from v1.20.0 to v1.24.0.
.github/workflows/test.yml	Updated versions for multiple actions: actions/checkout from v4.1.1 to v4.1.6, and davelosert/vitest-coverage-report-action from v2 to v2.3.1.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f822bc2 and 33ce6a6.

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)

Files skipped from review due to trivial changes (4)

• .github/workflows/assign.yml
• .github/workflows/deploy.yml
• .github/workflows/github_actions_version_updater.yml
• .github/workflows/test.yml

Additional comments not posted (3)

.github/workflows/push_code_linting.yml (3)

35-35: Update to actions/checkout@v4.1.6 looks good. Ensure to check the release notes for any breaking changes or new features that might require adjustments.

---

47-47: Update to reviewdog/action-eslint@v1.24.0 looks good. Ensure to check the release notes for any breaking changes or new features that might require adjustments.

---

43-43: Update to xt0rted/markdownlint-problem-matcher@v3.0.0 looks good. Ensure to check the release notes for any breaking changes or new features that might require adjustments.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.