Match Packagist distribution in PHP release smoke

[karlwaldman]

Summary

• release PHP SDK 2.1.2 after the immutable 2.1.1 Packagist dist exposed a local-vs-public archive mismatch
• add Git export-ignore rules for development-only workflows, tests, and validators so GitHub/Packagist source archives contain only customer package surfaces
• make the clean-install gate install a GitHub-shaped git archive, recursively validate all 16 installed readable text surfaces, and reject stale Client::VERSION

Red / green evidence

• Red public proof: a no-cache composer require oilpriceapi/oilpriceapi:2.1.1 resolved exact b4527acdcf10e20a14347c632fdd02d06877ad74, then the exhaustive validator failed on development-only .github, tests, and scripts files that local composer archive had excluded.
• Red unit proof: testPackagedSmokeScansTheExactGitHubDistribution failed because the gate still used composer archive and no .gitattributes existed.
• Green: 26 tests / 321 assertions; strict Composer validation; Git archive contains only README/CHANGELOG/LICENSE/composer, examples, and src; exact archive clean install validates 16 surfaces and covers success, missing config, 401, 403, and 429.

Release safety

• v2.1.1 remains immutable and is marked superseded/prerelease; no tag was deleted or moved.
• publish v2.1.2 only after this exact head is merged through protected main and main CI is green, then verify the public Packagist dist cold with keyless and authenticated production requests.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 3 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 Plus

Run ID: 1799103b-57ac-4f63-8ecb-fa4cbe44cc0d

📥 Commits

Reviewing files that changed from the base of the PR and between b4527ac and fe91169.

📒 Files selected for processing (6)

• .gitattributes
• .github/workflows/test.yml
• CHANGELOG.md
• scripts/clean-install-smoke.sh
• src/Client.php
• tests/PublicClaimsTest.php

---

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