Update GitHub Actions checkout from v3 to v4

[leopardracer]

This PR updates the GitHub Actions checkout action from version 3 to version 4 in the package version check workflow.

Changes:

• Updated actions/checkout@v3 to actions/checkout@v4 in check-package-version.yml

This update ensures we're using the latest stable version of the checkout action, which includes performance improvements and bug fixes.

Summary by CodeRabbit

• Chores
  • Upgraded the GitHub Actions workflow to use the latest version of the checkout action for improved reliability.

[coderabbitai]

Walkthrough

The GitHub Actions workflow configuration for checking package version updates was updated to use a newer version of the checkout action, specifically upgrading from version 3 to version 4. No other aspects of the workflow, including steps or logic, were altered.

Changes

File(s)	Change Summary
.github/workflows/check-package-version.yml	Upgraded checkout action from v3 to v4 in workflow

Poem

A hop to version four,
In workflows we explore,
The checkout step is shiny new,
Our CI hops along, right on cue!
With YAML neat and actions bright,
The package check runs just right.
🐇✨

---

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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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.

CodeRabbit Configuration 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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 671dcea and a23d6e9.

📒 Files selected for processing (1)

• .github/workflows/check-package-version.yml (1 hunks)

[coderabbitai]

🧹 Nitpick (assertive)

Upgrade to checkout@v4 looks correct
Pinning to the v4 major release ensures you benefit from the latest performance improvements and bug fixes.

Consider enabling full history for version-check
The EndBug/version-check action compares changes across branches; adding fetch-depth: 0 will fetch the entire git history and make the diff reliable.

      - name: Checkout
-       uses: actions/checkout@v4
+       uses: actions/checkout@v4
+       with:
+         fetch-depth: 0

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	uses: actions/checkout@v4
	- name: Checkout
	uses: actions/checkout@v4
	with:
	fetch-depth: 0