fix(examples): regenerate stale index.js to unblock the Examples drift check on main - #578
Conversation
…ngibles/create The Examples drift check has failed on main since #542. The CLI source files for these two examples were updated without regenerating their generated index.js, so CI's build-examples run produces a diff. Ran node scripts/build-examples.js; only these two files change. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NNz9JwDB9mhCzMU4Xbs45F
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 🧰 Additional context used📚 Code guidelines (1)No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. Summary by CodeRabbit
WalkthroughThe CLI examples add commands that specify mint keypair files for asset and fungible-token creation. The asset example changes its metadata option from ChangesCLI creation examples
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~4 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The examples match the documented CLI options, with no concrete merge-blocking risk identified. The PR is ready for normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Why
The Examples drift workflow is failing on
main, and every open PR that runs it inherits the failure. It regeneratessrc/examples/**/index.jswithbuild-examplesand fails if the result differs from what is committed.mainat9f3535a(feat mpl-core-das updates #542, "feat mpl-core-das updates", merged 2026-09-30 17:45Z): Examples drift failed.mainrun at8b8c55f(Add tx v1 umi documentation #567): passed.checkjob (run 36755897925) fails withsrc/examples/**/index.js is out of sync with its source files.The two files that differ are
src/examples/core/create-asset/index.jsandsrc/examples/token-metadata/fungibles/create/index.js. Their CLI source files already contain changes that the committedindex.jsdoes not reflect.What
Ran
node scripts/build-examples.json currentmainand committed the result. Only those two generated files change (2 lines, 1 per file), and both changes are generated output of source already onmain:core/create-asset:--jsonbecomes--offchainin the files example, and a vanity asset address example is added.token-metadata/fungibles/create: adds a vanity mint address example.No source files and no docs pages are edited.
Why a reviewer is needed
You wrote #542 and the CLI example changes, so you are best placed to confirm two things:
--offchainis the intended flag formplx core asset create --files, and that the vanity examples (--mint-keypair) should ship. The regenerated output publishes them as they are in the sources.Merging this is also what unblocks the checks on #562, #563 and #572, so a quick review helps those PRs too.
Verification
git diffshows only the two files above.pnpm run build; this changes generated example data only.🤖 Generated with Claude Code
https://claude.ai/code/session_01NNz9JwDB9mhCzMU4Xbs45F
Generated by Claude Code