chore(card-data): refresh MTGJSON token & subtype catalogs - #6849
Conversation
|
Warning Review limit reached
Next review available in: 2 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Comment |
Parse changes introduced by this PR✓ No card-parse changes detected. |
Automated refresh of the engine-embedded card-data catalogs from the latest MTGJSON publish.
crates/engine/data/known-tokens.toml— named-token catalog (tokens-gen)crates/engine/data/oracle-subtypes.json— creature-subtype vocabulary (oracle-gen --write-subtypes)crates/engine/data/mtgjson-vintage— vintage write-gate stampGenerated by
PHASE_REFRESH_MTGJSON=1 scripts/gen-card-data.sh; the vintage gate only promotes catalogs when the MTGJSON input date advances, so this diff reflects a genuine upstream data change. Review, then let it auto-merge once CI is green.