chore(cli): release 2.1.0

[waleedlatif1]

Summary

The merged CLI work is not published. sim@latest on npm is still the pre-fix 2.0.0, so every fix and feature from the last several PRs is on main but not in anyone's hands.

Verified against production with the published binary:

$ sim tables mkdir '/prod-probe'      # sim@latest, default endpoint
Error: Workspace ID is required       # the apex-redirect bug, still live

Nothing was created — the body was dropped by the sim.ai → www.sim.ai redirect. Reads work, which is what makes it so hard to spot.

Cause. publish-sim-cli.yml derives the npm version from package.json, and on main it uses it verbatim. 2.0.0 was already on the registry, so the guarded publish step skipped:

Skipped sim@2.0.0 because that version is already published.

staging and dev append -preview.N / -dev.N, so they always publish — main is the only branch where a missing version bump silently ships nothing, and the run still reports success.

Minor, not patch: three commands are new (workflows run --follow, workflows runs wait, logs follow) and the built-in default endpoint changed.

Type of Change

• Chore

Testing

--version reports 2.1.0 and the User-Agent picks it up (sim-cli/2.1.0 node/22.19.0 (darwin; arm64)) — the version is read from package.json at runtime, so the two cannot drift.

Suite is 428 passed / 1 skipped. lint, type-check, build, check:cli-docs and all 29 audits pass.

Note for a follow-up

A skipped publish on main is indistinguishable from a successful one in the Actions UI — both are a green check. Worth failing the job when main resolves to an already-published version, rather than letting a forgotten bump look like a release. Not included here to keep this change to the bump itself.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 18, 2026 10:29pm

[cursor]

PR Summary

Low Risk
Single version field change with no runtime logic; risk is operational (ensuring publish succeeds) rather than code behavior in this diff.

Overview
Bumps sim CLI from 2.0.0 to 2.1.0 in packages/sim-cli/package.json so the main publish workflow can push a new npm version instead of skipping because 2.0.0 is already on the registry.

Runtime --version and User-Agent read this field, so the published binary will report 2.1.0 and ship the CLI fixes and features already on main (including default endpoint and new workflow/log commands) that were never released under 2.0.0.

^{Reviewed by Cursor Bugbot for commit e288bb5. Configure here.}

[greptile-apps]

Greptile Summary

This PR releases the accumulated CLI changes by increasing the sim package version from 2.0.0 to 2.1.0.

• Updates the npm package version used by the publishing workflow.
• Updates the runtime version reported by --version and the CLI User-Agent through the shared package manifest.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete blocking or non-blocking defects identified in the version bump.

The publishing workflow and runtime version reporting both derive their version from the changed package manifest, and no established release inconsistency remains.

Important Files Changed

Filename	Overview
packages/sim-cli/package.json	Bumps the CLI package to version 2.1.0 so the release workflow can publish the accumulated changes under a new npm version.

_{Reviews (1): Last reviewed commit: "chore(cli): release 2.1.0" | Re-trigger Greptile}