release(cli): cut v0.2.5#4055
Conversation
Two cli-v0.2.4 regressions fixed: - pty-daemon.js never bundled into the dist tarball — supervisor bricked at spawn with `script not found at /home/pty-daemon/dist/pty-daemon.js` on every fresh install (#4054). - OAuth access tokens (CLI auth login default) sent to better-auth's /api/auth/token endpoint, which only handles sessions/api keys → 401 on relay JWT mint (#4054). Push cli-v0.2.5 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 ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughCLI package version bumped from 0.2.4 to 0.2.5 in both the configuration constant and package manifest. The version propagates to environment variables and exported configuration. ChangesCLI Version Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
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. Comment |
Greptile SummaryThis PR cuts the Confidence Score: 5/5Safe to merge — all three version references are consistent and no logic is changed. Only version strings are modified across three files, all consistently updated to 0.2.5. No logic, dependencies, or configuration values are changed beyond the version bump. No files require special attention.
|
| Filename | Overview |
|---|---|
| packages/cli/package.json | Version bumped from 0.2.4 to 0.2.5 — consistent with other changed files |
| packages/cli/cli.config.ts | VERSION constant updated from "0.2.4" to "0.2.5" — consistent with package.json |
| bun.lock | Lockfile version for @superset/cli bumped from 0.2.4 to 0.2.5 to reflect package.json change |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["PR #4055 merges"] --> B["Push cli-v0.2.5 tag"]
B --> C[".github/workflows/release-cli.yml triggers"]
C --> D["Matrix build: 3 targets"]
D --> E["Artifacts published\n(lib/host-service.js + lib/pty-daemon.js)"]
E --> F["Release tarball available"]
Reviews (1): Last reviewed commit: "release(cli): cut v0.2.5" | Re-trigger Greptile
🚀 Preview Deployment🔗 Preview Links
Preview updates automatically with new commits |
1 participant
Summary
@superset/clito v0.2.5 (packages/cli/package.json,cli.config.ts,bun.lock).build-dist.tsonly builthost-service.js, host-service supervisor crashed at spawn withscript not found at /home/pty-daemon/....JwtApiAuthProviderPOSTed the OAuth access token to better-auth's/api/auth/token, which only accepts session tokens / api keys. The token is already a JWT signed by the relay's JWKS, so we now pass it through.Release plan
After this PR merges, push the
cli-v0.2.5tag to fire.github/workflows/release-cli.yml.Test plan
lib/host-service.jsandlib/pty-daemon.jssuperset auth login→superset startshould connect to the relay (noFailed to mint JWT: 401) and the supervisor should bootstrap (noscript not founderror)Summary by cubic
Release
@superset/cliv0.2.5 to fix two v0.2.4 regressions: thepty-daemonwas not bundled, and OAuth logins failed with 401s when minting relay JWTs.lib/pty-daemon.jsin the dist so the supervisor can spawn it (no more “script not found” on fresh installs).JwtApiAuthProviderto pass through the OAuth access token (relay-signed JWT) instead of POSTing to/api/auth/token, preventing 401s during relay auth.Written for commit 02808e5. Summary will update on new commits.
Summary by CodeRabbit