Update GitHub action version

[alistair3149]

Fix deprecated version in GitHub workflow

Summary by CodeRabbit

• Chores
  • Enhanced the continuous integration process by updating key tools for caching and repository management. This improvement boosts performance, stability, and reliability in the build process, contributing to a more efficient development pipeline. While these updates are internal, they help ensure a smoother and more robust experience overall.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the version references in the CI workflow configuration. Specifically, it upgrades the GitHub Actions used for caching and checking out the repository by switching from version v2 to v4. These updates occur in multiple steps, including caching for MediaWiki and Composer, as well as for the repository checkout process. There are no changes to the logical flow or public APIs.

Changes

File	Change Summary
.github/workflows/ci.yml	Upgraded GitHub Actions versions: updated actions/cache from v2 to v4 and actions/checkout from v2 to v4 in multiple workflow steps.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c25717c and 9c8db6f.

📒 Files selected for processing (1)

• .github/workflows/ci.yml (12 hunks)

🔇 Additional comments (4)

.github/workflows/ci.yml (4)

56-79: Updated GitHub Actions Versions in Test Job Steps
The caching and checkout actions in the Test job have been correctly upgraded from v2 to v4. The changes on lines 56 (cache for MediaWiki), 65 (cache for Composer), 70 (checkout for EarlyCopy), and 79 (checkout for AutomatedValues) are consistent and align with current best practices. Please verify that the new versions work seamlessly with your workflows and that the cache keys (e.g. including “_v4” in the key) continue to deliver the intended caching behavior.

---

125-148: Updated GitHub Actions Versions in PHPStan Job Steps
The PHPStan job’s steps now use actions/cache@v4 (lines 125 and 134) and actions/checkout@v4 (lines 140 and 148). These updates ensure consistency across jobs and conform to the updated GitHub Actions recommendations. No further action is necessary unless you encounter runtime issues with the new versions.

---

185-208: Updated GitHub Actions Versions in Psalm Job Steps
The Psalm job steps have been updated with actions/cache@v4 on lines 185 and 194 and actions/checkout@v4 on lines 200 and 208. This maintains uniformity with the other jobs and addresses the deprecation of older versions. It is recommended to double-check that these updates do not affect the working-directory settings or any other job-specific configurations.

---

245-264: Updated GitHub Actions Versions in Code Style Job Steps
The Code style job now uses actions/cache@v4 (lines 245 and 254) and the checkout action has been updated to v4 on line 264. These modifications are straightforward and adhere to the primary objective of updating deprecated action versions. Please test the workflow to ensure that the new versions maintain the same behavior as before.

---

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.

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.