From d0427e04ee7ee1fa4681f8c539f7f60298b318c6 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 30 Jul 2026 22:40:24 +0800 Subject: [PATCH] chore: bump to 0.0.23-rc.1 for the first prerelease MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The staging install channel (install.sh --staging, insta-cli#66) resolves the newest PRERELEASE, and none has ever been published — so `--staging` currently falls back to stable v0.0.22, which predates `insta env` and therefore hard-fails by design. Release binaries take their version from the tag (INSTA_CLI_VERSION), but publish-npm runs a bare `npm publish`, which uses package.json — so tagging v0.0.23-rc.1 without this bump would try to republish 0.0.22 and fail the npm job. Being hyphenated, this version publishes with --prerelease on the GitHub release and under npm's `next` dist-tag, so it stays off /releases/latest and off npm latest: production installers are unaffected. --- package-lock.json | 4 ++-- package.json | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/package-lock.json b/package-lock.json index be657a3..3aa003e 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "insta-cli", - "version": "0.0.0", + "version": "0.0.23-rc.1", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "insta-cli", - "version": "0.0.0", + "version": "0.0.23-rc.1", "dependencies": { "commander": "^12.1.0" }, diff --git a/package.json b/package.json index 37437cc..ed5f5c3 100644 --- a/package.json +++ b/package.json @@ -1,8 +1,8 @@ { "name": "insta", - "version": "0.0.22", + "version": "0.0.23-rc.1", "type": "module", - "description": "InstaCloud CLI \u2014 a thin client of the platform control-plane API.", + "description": "InstaCloud CLI — a thin client of the platform control-plane API.", "keywords": [ "insta", "insforge",