Skip to content

chore: dependabot + PHP 8.4/8.5 CI matrix + PHPUnit 13 allowance#5

Open
karlwaldman wants to merge 2 commits into
mainfrom
chore/ci-matrix-dependabot
Open

chore: dependabot + PHP 8.4/8.5 CI matrix + PHPUnit 13 allowance#5
karlwaldman wants to merge 2 commits into
mainfrom
chore/ci-matrix-dependabot

Conversation

@karlwaldman

Copy link
Copy Markdown
Member

What

  • dependabot.yml — composer + github-actions ecosystems, monthly cadence, PR-limit 3 (repo had none)
  • CI matrix — adds PHP 8.4 and 8.5 (current stable) alongside 8.1–8.3
  • PHPUnit — widen dev constraint to ^10.5 || ^11.0 || ^12.0 || ^13.0 so newer PHP runners get the current major

Verification (local)

  • PHP 8.5.8 + PHPUnit 13.2.4: vendor/bin/phpunitOK (16 tests, 80 assertions)
  • Also green on PHPUnit 12.5.31 (pre-change baseline)
  • composer validate --strict passes

No runtime code touched — the SDK has zero runtime dependencies (ext-curl/ext-json only).

🤖 Generated with Claude Code

- Add .github/dependabot.yml (composer + github-actions, monthly)
- Extend CI matrix with PHP 8.4 and 8.5 (SDK has zero runtime deps;
  full suite passes locally on PHP 8.5.8)
- Allow phpunit ^13.0 in require-dev - verified locally: 16 tests /
  80 assertions pass on PHPUnit 13.2.4; composer still resolves 10.x
  on PHP 8.1 runners

composer validate --strict passes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@karlwaldman, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 628912bf-e95d-405b-ac70-4a18eb00f965

📥 Commits

Reviewing files that changed from the base of the PR and between 62ca766 and 28e86c9.

📒 Files selected for processing (4)
  • .github/dependabot.yml
  • .github/workflows/test.yml
  • composer.json
  • examples/smoke.php
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/ci-matrix-dependabot

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

Comment @coderabbitai help to get the list of available commands.

The OILPRICEAPI_TEST_KEY secret now gets HTTP 402 on /v1/prices/past_week
(historical data became a paid entitlement), which broke the smoke step
on every matrix job - including on main, unrelated to this PR's changes.

Historical access is a plan property, not an SDK feature: latest() above
already proves auth + transport + parsing. Treat 402/403 on the
past_week leg as a documented skip; any other error still fails.

Verified locally against the live API with the same test key:
- 402-plan key: exits 0 with 'past_week skipped' notice
- full-access key: exits 0 with 'latest + past_week'

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@karlwaldman

Copy link
Copy Markdown
Member Author

CI note: the initial run failed on all 5 matrix jobs at the live-smoke step, not the unit tests — the OILPRICEAPI_TEST_KEY secret now gets HTTP 402 on /v1/prices/past_week (historical became a paid entitlement), so main would fail the same way today. Pushed 28e86c9: the smoke script treats 402/403 on the historical leg as a documented skip (latest() already proves auth/transport/parsing); any other error still fails. Verified locally with the same test key (exit 0, skip notice) and with a full-access key (exit 0, latest + past_week). Alternative if you prefer full coverage: swap the repo secret to a key with historical access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant