Remove nonexistent telemetry quota bonus claim - #68
Merged
Conversation
📝 WalkthroughWalkthroughThe package now rejects telemetry or application-metadata quota-reward claims, updates related wording to usage attribution, and releases version 1.2.5 with matching metadata and tests. ChangesTelemetry claim validation and release update
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/validate-storefront-claims.mjs`:
- Around line 29-32: The quota-reward pattern in the storefront claims validator
must distinguish quota entitlements from attribution-only metadata in request
context. Update the regex near “telemetry quota reward” so the reward term is
associated with the quota entitlement rather than merely the metadata payload;
preserve detection of genuine extra API quota claims. In
tests/storefront-claims.test.ts lines 123-145, add the request-context
attribution fixture and assert validatePackage(root) returns [].
In `@src/types.ts`:
- Line 54: Update the appName documentation in the relevant interface in
src/types.ts to describe it as being used for usage attribution, matching the
corresponding header descriptions in src/client.ts. Remove the conflicting “for
telemetry” wording while preserving the existing optional application URL
description.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 01d9b45b-a8d6-470a-869f-b734357e802b
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (8)
CHANGELOG.mdpackage.jsonscripts/validate-storefront-claims.mjssrc/client.tssrc/types.tssrc/version.tstests/release-readiness.test.tstests/storefront-claims.test.ts
karlwaldman
force-pushed
the
codex/remove-telemetry-bonus-claim
branch
from
August 12, 2026 09:34
945423a to
381eedf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
1.2.5Red / green
Red first:
.d.tstelemetry-bonus fixtures, including the exact released spellings, failed before the guardTelemetry sends extra application metadata with API requests.failed against the first matcher and now remains an explicit allowed attribution-only regressionGreen on replacement exact head
381eedf13e4997a545ba110709f67264e647e1eb(tree652273d19eab420d17d94e006c2dcb028fc7c6cd):npm test: 34 files, 499 passed, 1 skippednpm run buildnpm run storefront:check: 36 public surfacesnpm run snippets:check: 6 fixtures + 4 manifest testsnpm run lintnpm run check:secretsnpx tsc --noEmitnpm audit --audit-level=low: 0 vulnerabilitiesnpm run smoke:package: clean packed ESM/CJS production keyless smokeExact replacement local candidate
oilpriceapi-1.2.5.tgz:961fdb334f2aa639dceb88cefddebc895f706d9esha512-3po0h0aCbyUIrBq5OhEIfxgXTkjiSJDS94SepTw6+4QBtSXsaoBHyID2RnHRw74cf7D7ugIllr0VcKDq9HpHxw==The earlier
945423afcandidate and its local tarball hashes are superseded.Release
Merge through protected main, then publish immutable
v1.2.5only through the existing reviewed OIDC workflow. Public npm integrity/provenance and clean ESM/CJS authenticated + keyless smokes remain release gates.