Skip to content

fix(cli): SDK pin for hybrid tier commands; prepare first npm prerelease - #65

Merged
purpshell merged 1 commit into
devfrom
t3code/cli-first-release
Oct 2, 2026
Merged

purpshell merged 1 commit into
devfrom
t3code/cli-first-release

Conversation

@purpshell

@purpshell purpshell commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

Why

dev (72325fa) does not build: #35 uses NumberHybridTransition, listHybridMergeCandidates and the hybrid quote fields, which first shipped in @polymorfa/sdk@0.1.0-dev.20261002023214. The CLI still pinned 0.1.0-dev.20261001215108, so npm ci (which runs prepare → build) fails with TS2305/TS2339.

This unblocks the first npm prerelease of @polymorfa/cli (0.1.0-dev.0, dev tag).

Changes

  • Pin @polymorfa/sdk to exactly 0.1.0-dev.20261002023214 (package.json + lockfile).
  • test/release/check-prerelease.test.ts reads the pinned SDK from package.json instead of a hardcoded version, so future pin bumps don't break the guard test.
  • README: document npm install --global @polymorfa/cli@dev; the GitHub install stays for repository members.

Verification

  • node scripts/check-prerelease.mjs 0.1.0-dev.0 passes.
  • npm run verify passes: format, lint, typecheck, 1003/1003 tests, build, npm pack --dry-run, npm audit --omit=dev (0 vulnerabilities).
  • Packed tarball installed into a clean prefix: polymorfa version --json → {"cli":"0.1.0-dev.0","sdk":"0.1.0-dev.20261002023214"}. Tarball holds only bin/run.js, dist/, skills/, README.md, LICENSE, package.json.

Six-part assessment

  • API: unaffected; no request or route changes.
  • SDKs: unaffected; consumes an already-published SDK prerelease.
  • CLI: updated; the build is fixed and the install docs changed.
  • Docs: the public CLI page (docs/tools/cli-api.mdx in the monorepo) still says the package is unpublished. It gets updated in a monorepo PR once the package is live on npm.
  • Feature releases: no flag. Publishing goes to the dev dist-tag only.
  • Admin controls: unaffected; no customer state.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.

…prepare first npm prerelease

PR #35 merged hybrid tier commands that use SDK exports first published in
0.1.0-dev.20261002023214, so the dev head failed to build against the
previous pin. The release guard test now derives the pinned SDK from
package.json instead of hardcoding it, and the README documents the npm
dev-tag install.
@coderabbitai

coderabbitai Bot commented Oct 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

The included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.

  • Ask an admin to enable usage-based reviews

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Next included review available in 35 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available. Your 71 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: ad37ba6b-de83-4d80-8eb5-46cfb5c3b971

📥 Commits

Reviewing files that changed from the base of the PR and between 72325fa and ed04907.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • README.md
  • package.json
  • test/release/check-prerelease.test.ts
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


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

@purpshell
purpshell merged commit fc38156 into dev Oct 2, 2026
3 checks passed
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.

1 participant