fix: drop venue-typed source enums; align examples with market_reporting (#4175)

[karlwaldman]

What & why

Part of the SDK-fleet sweep for oilpriceapi-api#4175. The API is switching masked source labels to market_reporting (government labels like EIA/opec.org unchanged). This aligns the Node/TypeScript SDK.

Typing

No enum to loosen — FuturesPrice.source (and all source fields) are already string. So nothing breaks when the API starts returning market_reporting.

Examples/fixtures fixed

• src/resources/futures.ts: doc comment Data source (e.g. "ICE") → Data source label (e.g. "market_reporting", or a government label like "EIA").
• tests/resources/futures.test.ts: fixture source: "ICE" → source: "market_reporting".

Left unchanged intentionally: ice-brent/ice-wti are route path slugs (/v1/futures/{slug}), not source labels — those belong to the futures route-alias work, not this issue. types.ts example "oilprice.ft" is not a venue.

Version (unpublished)

• 1.0.1 → 1.0.2 in package.json, CHANGELOG entry added. Not published to npm.

Test/build

• npm run build (tsc + cjs): passes.
• npm test -- futures (vitest): 64/64 pass.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 57 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: f1c53153-2ead-4472-a63e-9f49d4938bdd

📥 Commits

Reviewing files that changed from the base of the PR and between 203730e and 97f202a.

📒 Files selected for processing (5)

• CHANGELOG.md
• package.json
• src/resources/futures.ts
• src/version.ts
• tests/resources/futures.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-4175-source-labels

---

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