add php 8.4 support and bump workflow actions

[akondas]

Summary by CodeRabbit

• Chores
  • Updated automated build process to test with PHP 8.4 in addition to 8.3.
  • Upgraded components of the build workflow for improved reliability and compatibility.

[coderabbitai]

Walkthrough

The GitHub Actions build workflow was updated to add PHP 8.4 to the test matrix, upgrade the checkout action from version 2 to 4, and upgrade the composer-install action from version 2 to 3. No changes were made to code, logic, or exported entities.

Changes

File(s)	Change Summary
.github/workflows/build.yml	Added PHP 8.4 to test matrix, upgraded checkout and composer actions

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• drop support for php 8.1 and 8.2 #9: Both PRs modify the GitHub Actions workflow's PHP version matrix, with the main PR adding PHP 8.4 and the retrieved PR removing PHP 8.1 and 8.2, indicating related changes to the CI configuration.

Poem

🐇
The build hops forward, swift and neat,
With PHP 8.4 beneath its feet.
Actions upgraded, matrix grown,
Composer and checkout now full-blown.
CI’s garden, fresh and bright—
The code hops on, all tests in sight!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate unit tests to generate unit tests for 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: 0

🧹 Nitpick comments (2)

.github/workflows/build.yml (2)

11-12: Confirm nightly availability or mark PHP 8.4 as an allowed-failure target

shivammathur/setup-php will attempt to install the latest nightly/dev build for a future minor (8.4) until it is officially released. Nightlies can break unexpectedly and fail the entire job.

Consider guarding against that by either:

      matrix:
        php-version:
           - "8.3"
-          - "8.4"
+          - "8.4"
+    fail-fast: false          # don’t cancel the matrix on the first failure
+
+  build:
+    continue-on-error: ${{ matrix.php-version == '8.4' }}

(or splitting the 8.4 job into a separate, allow-failure build).
This keeps stable branches green while still getting early signal from 8.4.

---

25-27: Composer-install v3 upgrade: double-check cache keys

ramsey/composer-install@v3 changed its default cache key structure. If you rely on the old v2 key to share cache with other workflows you might see a cold-cache and longer install times on the first run.

Nothing to fix here, just be aware and monitor the first pipeline run after merge.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d098aed and 6d683ee.

📒 Files selected for processing (1)

• .github/workflows/build.yml (2 hunks)

🔇 Additional comments (1)

.github/workflows/build.yml (1)

17-17: Checkout v4 looks good

Upgrade to actions/checkout@v4 is compatible and benefits from the Node 20 runtime. No additional changes required.