release(cli): cut v0.2.0, fix install.sh latest URL#3917
Conversation
The install.sh latest path was pointing at /releases/latest/download/, which GitHub resolves to the highest non-prerelease release across the whole repo — almost always a desktop-v* release. CLI tarballs aren't in those, so curl | sh 404s. release-cli.yml already maintains a rolling cli-latest release that's re-pointed on every cli-v* tag publish. Switch install.sh to read from that path so it never collides with desktop releases. Bump CLI version 0.1.0 -> 0.2.0 to capture all the changes since April 9 (host flag rework, prompt split, automations prompt subcommand, API key path rename, install/release pipeline rewrite). Push cli-v0.2.0 after this lands to fire the release pipeline.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughVersion bump from 0.1.0 to 0.2.0 across CLI package, configuration, and build scripts. Installation script updated to download from an explicit release tag endpoint instead of the generic latest endpoint. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 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. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
Greptile SummaryThis PR bumps the CLI from Confidence Score: 5/5Safe to merge — all three changes are minimal, consistent, and correct. The URL fix in No files require special attention.
|
| Filename | Overview |
|---|---|
| apps/marketing/public/cli/install.sh | Fixes the default download URL from the repo-wide /releases/latest/download/ (which resolves to a non-CLI tag) to the dedicated rolling cli-latest release tag; the rest of the script is unchanged. |
| packages/cli/cli.config.ts | Version constant bumped from 0.1.0 to 0.2.0 — consistent with package.json. |
| packages/cli/package.json | Package version bumped from 0.1.0 to 0.2.0 — consistent with cli.config.ts. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["curl install.sh | sh"] --> B{TAG == 'latest'?}
B -- "Yes (default)" --> C["URL: /releases/download/cli-latest/superset-{target}.tar.gz\n✅ Fixed — resolves to CLI assets"]
B -- "No (SUPERSET_VERSION set)" --> D["URL: /releases/download/{TAG}/superset-{target}.tar.gz\n(unchanged)"]
C --> E["curl -fsSL download"]
D --> E
E --> F["extract to ~/superset/"]
F --> G["verify binaries executable"]
G --> H["update PATH in shell profile"]
H --> I["Done ✅"]
Reviews (1): Last reviewed commit: "release(cli): cut v0.2.0, fix install.sh..." | Re-trigger Greptile
🚀 Preview Deployment🔗 Preview Links
Preview updates automatically with new commits |
Already integrated, superseded by current versions, or net-empty in this fork: superset-sh#3881 superset-sh#3887 superset-sh#3917 superset-sh#3925 superset-sh#3940 superset-sh#3956 superset-sh#3961 superset-sh#3974 superset-sh#4017 superset-sh#4048 superset-sh#4049 superset-sh#4055 superset-sh#4063 superset-sh#4070 superset-sh#4092 superset-sh#4110 superset-sh#4138 superset-sh#4159 superset-sh#4163 superset-sh#4164 superset-sh#4209 superset-sh#4210 superset-sh#4249 superset-sh#4349 superset-sh#4405 superset-sh#4462 superset-sh#4464 superset-sh#4494 superset-sh#4495 superset-sh#4500 superset-sh#4535 superset-sh#4541 superset-sh#4566 superset-sh#4580 superset-sh#4589 superset-sh#4593 superset-sh#4603 superset-sh#4637 superset-sh#4642 superset-sh#4655 superset-sh#4657 superset-sh#4659 superset-sh#4685 superset-sh#4692 superset-sh#4745 superset-sh#4789 superset-sh#4797 superset-sh#4824 superset-sh#4835 superset-sh#4847 superset-sh#4885 superset-sh#4896.
Summary
install.shfrom/releases/latest/download/(which resolves to the highest non-prerelease repo-wide — usuallydesktop-v*, no CLI assets, 404) to the rollingcli-latestrelease thatrelease-cli.ymlmaintains. This is what the workflow already expects;install.shwas just stale.0.1.0→0.2.0to cover the 16 commits since April 9:--host/--localhost flags,automations promptsubcommand andsetPromptsplit,--to→--versionrename,sk_live_→x-api-keyheader fix,CLOUD_API_URL→SUPERSET_API_URLrename, release pipeline rewrite (rollingcli-latest+ Homebrew bump).After this merges, push
cli-v0.2.0from main to firerelease-cli.yml→ versioned--prerelease+ rollingcli-latest+ auto Homebrew formula bump viabump-homebrew.yml.Test plan
git tag cli-v0.2.0 && git push origin cli-v0.2.0from mainrelease-cli.ymlgo green (~3-5 min for the matrix build)curl -sI -L https://github.com/superset-sh/superset/releases/download/cli-latest/superset-darwin-arm64.tar.gz | head -1→ 200/302curl -sI -L https://github.com/superset-sh/superset/releases/download/cli-latest/superset-linux-x64.tar.gz | head -1→ 200/302curl -sI -L https://github.com/superset-sh/superset/releases/download/cli-latest/superset-linux-arm64.tar.gz | head -1→ 200/302curl -fsSL https://superset.sh/cli/install.sh | shcompletes without errorsuperset --versionprints0.2.0bump-homebrew.ymlran, formula insuperset-sh/homebrew-tapupdated to0.2.0with correct SHA256sbrew upgrade superset(orbrew install) on a clean machine pulls 0.2.0Summary by CodeRabbit