Repository navigation
chore(cli): bump version to 0.2.23 — fix #5294 stale binary version - #5296
Conversation
Cuts a clean release so users stuck on the mis-baked cli-v0.2.22 binary (which reports 0.2.19) finally update. The hardcoded-version root cause is already fixed on main (cli.config.ts derives VERSION from package.json), so a tag at this commit bakes the correct version. Closes #5294
|
Ready to review this PR? Stage has broken it down into 1 individual chapter for you:
Chapters generated by Stage for commit 3d8693f on Jun 17, 2026 7:15pm UTC. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe ChangesCLI Version Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
🚀 Preview Deployment🔗 Preview Links
Preview updates automatically with new commits |
What
Bumps
@superset/clito 0.2.23 and cuts a clean release.Why (#5294)
The
cli-v0.2.22release shipped binaries that report0.2.19(verified by downloading the darwin-arm64 asset:superset --version→0.2.19). Root cause: at that tag,packages/cli/cli.config.tshad a hardcodedconst VERSION = "0.2.19"that had drifted frompackage.json. Because the rollingcli-latest/version.txtis derived from the tag (correctly0.2.22),superset update --checkcompares0.2.19(binary) vs0.2.22(latest) and is permanently stuck on 'update available'.The hardcode is already fixed on
main—cli.config.tsnow derivesconst VERSION = pkg.version. So all that's needed to unstick users is a clean version bump + fresh tag: the build will bake the correct version, the newversion.txtwill advertise it, and stuck0.2.19binaries will update normally.Release
After merge, cut the
cli-v0.2.23tag to triggerrelease-cli.yml.Closes #5294
Summary by cubic
Bump
@superset/clito 0.2.23 to ship a clean binary that reports the correct version. This resolves stale update checks fromcli-v0.2.22and unblocks users stuck on binaries reporting 0.2.19 (fixes #5294).Written for commit 3d8693f. Summary will update on new commits.
Summary by CodeRabbit