chore(card-data): refresh MTGJSON token & subtype catalogs - #7516
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan includes up to 2 reviews per rolling hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe vintage data date changes from ChangesMTGJSON vintage refresh
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized generated card-data refresh with no actionable merge-blocking risk remaining after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
|
Generated for head Parse changes introduced by this PR✓ No card-parse changes detected. |
3fea585 to
e5b59bf
Compare
cfd83e4 to
72794f3
Compare
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.