Skip to content

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

Merged
saddlepaddle merged 1 commit into
mainfrom
bump-cli-0.2.23
Jun 17, 2026
Merged

saddlepaddle merged 1 commit into
mainfrom
bump-cli-0.2.23

Conversation

@saddlepaddle

@saddlepaddle saddlepaddle commented Jun 17, 2026 •

Copy link
Copy Markdown
Collaborator

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).

Written for commit 3d8693f. Summary will update on new commits.

Review in cubic

Summary by CodeRabbit

  • Chores
    • Bumped CLI package version.

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
@ghost

ghost commented Jun 17, 2026

Copy link
Copy Markdown

Ready to review this PR? Stage has broken it down into 1 individual chapter for you:

Title
1 Bump CLI version to 0.2.23
Open in Stage

Chapters generated by Stage for commit 3d8693f on Jun 17, 2026 7:15pm UTC.

@coderabbitai

coderabbitai Bot commented Jun 17, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d4eff5cf-dc67-4bdb-85f5-1d91a4f5552d

📥 Commits

Reviewing files that changed from the base of the PR and between 30ab567 and 3d8693f.

📒 Files selected for processing (1)
  • packages/cli/package.json

📝 Walkthrough

Walkthrough

The version field in packages/cli/package.json is incremented from 0.2.22 to 0.2.23. No other files, scripts, dependencies, or configuration values are modified.

Changes

CLI Version Bump

Layer / File(s) Summary
CLI package version increment
packages/cli/package.json
@superset/cli version field updated from 0.2.22 to 0.2.23.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

Poem

🐇 A tiny hop, a version grown,
From .22 to .23 I've flown!
The CLI binary now tells the truth—
No more old numbers masking youth.
One line changed, the bug is gone,
The update checker hops along! 🎉

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the main change (version bump to 0.2.23) and references the issue being fixed (#5294).
Description check ✅ Passed The description provides clear context on what changed, why it was needed, and includes a reference to the linked issue #5294, though the template structure is not strictly followed.
Linked Issues check ✅ Passed The PR directly addresses issue #5294 by bumping the version to 0.2.23 and preparing a clean release that will resolve the stale binary version problem.
Out of Scope Changes check ✅ Passed The PR contains only a version bump in package.json, which is directly scoped to resolving issue #5294 and requires no unrelated changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bump-cli-0.2.23

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps

greptile-apps Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Bumps @superset/cli from 0.2.22 to 0.2.23 to fix a stale version string baked into the 0.2.22 binary. The root cause (a hardcoded const VERSION = "0.2.19" in cli.config.ts) is already resolved on main — cli.config.ts now derives VERSION from pkg.version — so this single-line bump is all that's needed to produce a correctly-versioned binary.

  • One-line diff: package.json version field changed from 0.2.22 → 0.2.23; cli.config.ts reads pkg.version dynamically, so no further changes are needed.
  • Release flow: After merge, pushing a cli-v0.2.23 tag triggers release-cli.yml, which builds all three platform targets, updates the rolling cli-latest release with the correct version.txt, and bumps the Homebrew formula.

Confidence Score: 5/5

Safe to merge — single-field version bump in package.json with no logic changes.

The change is exactly one field in one file. cli.config.ts already pulls VERSION from pkg.version, so the new binary will embed 0.2.23 correctly and unblock stuck auto-updaters. No behavioural, API, or dependency changes are introduced.

No files require special attention.

Important Files Changed

Filename Overview
packages/cli/package.json Version bumped from 0.2.22 to 0.2.23; no other changes. cli.config.ts already reads version dynamically from this file via pkg.version, so the new binary will correctly report 0.2.23.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub
    participant CI as release-cli.yml
    participant Bin as CLI Binary

    Dev->>GH: Merge PR (package.json 0.2.23)
    Dev->>GH: Push tag cli-v0.2.23
    GH->>CI: "Trigger on cli-v* tag"
    CI->>CI: Build darwin-arm64, linux-x64, linux-arm64
    CI->>GH: gh release create cli-v0.2.23
    CI->>GH: Update rolling cli-latest + version.txt (0.2.23)
    CI->>CI: Bump Homebrew formula
    Bin->>GH: superset update --check → reads cli-latest/version.txt (0.2.23)
    Bin->>Bin: "0.2.19 < 0.2.23 → downloads new binary"
    Bin->>Bin: superset --version → 0.2.23 ✓
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub
    participant CI as release-cli.yml
    participant Bin as CLI Binary

    Dev->>GH: Merge PR (package.json 0.2.23)
    Dev->>GH: Push tag cli-v0.2.23
    GH->>CI: "Trigger on cli-v* tag"
    CI->>CI: Build darwin-arm64, linux-x64, linux-arm64
    CI->>GH: gh release create cli-v0.2.23
    CI->>GH: Update rolling cli-latest + version.txt (0.2.23)
    CI->>CI: Bump Homebrew formula
    Bin->>GH: superset update --check → reads cli-latest/version.txt (0.2.23)
    Bin->>Bin: "0.2.19 < 0.2.23 → downloads new binary"
    Bin->>Bin: superset --version → 0.2.23 ✓
Loading

Reviews (1): Last reviewed commit: "chore(cli): bump version to 0.2.23" | Re-trigger Greptile

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

@github-actions

github-actions Bot commented Jun 17, 2026 •

Copy link
Copy Markdown
Contributor

🚀 Preview Deployment

🔗 Preview Links

Service Status Link
Neon Database (Neon) ✅ View Branch
Vercel API (Vercel) ✅ Open Preview
Vercel Web (Vercel) ✅ Open Preview
Vercel Marketing (Vercel) ✅ Open Preview
Vercel Admin (Vercel) ✅ Open Preview
Vercel Docs (Vercel) ✅ Open Preview

Preview updates automatically with new commits

This branch was previously deployed

1 inactive deployment
preview — 3d8693f4 Deployed Jun 17, 2026 by saddlepaddle via Deploy Docs #5989
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cli-v0.2.22 macOS arm64 tarball reports v0.2.19

1 participant