Update GitHub Actions to latest versions

[koriym]

Update actions/checkout, actions/cache, and codecov/codecov-action to their latest v4 versions.

Summary by CodeRabbit

• Chores
  • Upgraded continuous integration tooling to newer action versions to keep automation current and reliable; no behavioral changes to workflows.
  • Updated CI/static-analysis environment image and set PHP to 8.4 for analysis/build runs, aligning checks with a newer platform.

[coderabbitai]

Walkthrough

Updated CI configurations: GitHub Actions workflow action versions were bumped and the Scrutinizer CI image and PHP version were set. No exported/public API changes.

Changes

Cohort / File(s)	Summary
GitHub Actions workflow .github/workflows/continuous-integration.yml	Upgraded action versions: actions/checkout v1 → v4, actions/cache v2 → v4, and codecov-action v2 → v4; workflow steps and inputs preserved.
Scrutinizer CI config .scrutinizer.yml	Adds build environment settings: image: default-jammy and php: 8.4 for the build step; formatting whitespace tweak (empty line) only.

Sequence Diagram(s)

(omitted — changes are configuration-only and do not alter runtime control flow)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Check compatibility notes/changelogs for actions/checkout@v4, actions/cache@v4, and codecov-action@v4 against used inputs.
• Validate GitHub workflow runs (matrix jobs, caches) in CI after bump.
• Confirm Scrutinizer's default-jammy + php: 8.4 behaves as expected for project analysis.

Poem

🐰 I hopped through YAML, tidy and bright,

bumped the actions to newer light.
Jammy and PHP eight-point-four,
CI hums softly—hop once more! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change in the changeset—upgrading GitHub Actions to newer versions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update/github-actions

---

📜 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 bb36e20 and fb2669e.

📒 Files selected for processing (1)

• .scrutinizer.yml (1 hunks)

🔇 Additional comments (2)

.scrutinizer.yml (2)

1-11: Configuration structure and formatting look good.

The YAML syntax is correct, indentation is proper, and the configuration hierarchy is well-organized. The added empty line improves readability.

---

2-5: Verify the default-jammy image name is valid in Scrutinizer CI.

PHP 8.4 support is confirmed (Scrutinizer supports any released PHP versions). However, the specific image name default-jammy cannot be verified as a supported managed image in Scrutinizer's standard image inventory. While Scrutinizer offers a managed default image and Docker support, the naming convention default-jammy may not exist. Confirm this image name against current Scrutinizer documentation or test the build to ensure it works as expected.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[harikt]

Thank you @koriym .