chore(cli): bump version to 0.2.23 — fix #5294 stale binary version

Merged
SA
5mo ago
+1-1

What

Bumps @superset/cli to 0.2.23 and cuts a clean release.

Why (#5294)

The cli-v0.2.22 release shipped binaries that report 0.2.19 (verified by downloading the darwin-arm64 asset: superset --version → 0.2.19). Root cause: at that tag, packages/cli/cli.config.ts had a hardcoded const VERSION = "0.2.19" that had drifted from package.json. Because the rolling cli-latest/version.txt is derived from the tag (correctly 0.2.22), superset update --check compares 0.2.19 (binary) vs 0.2.22 (latest) and is permanently stuck on 'update available'.

The hardcode is already fixed on main — cli.config.ts now derives const 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 new version.txt will advertise it, and stuck 0.2.19 binaries will update normally.

Release

After merge, cut the cli-v0.2.23 tag to trigger release-cli.yml.

Closes #5294

Open in Stage

Summary by cubic

Bump @superset/cli to 0.2.23 to ship a clean binary that reports the correct version. This resolves stale update checks from cli-v0.2.22 and unblocks users stuck on binaries reporting 0.2.19 (fixes #5294).

Summary by CodeRabbit

  • Chores
    • Bumped CLI package version.