@jonaskahn/relo 0.1.9 → 0.1.10

package/lib/install.mjs

@@ -10,8 +10,8 @@
 // never waits on keys again.
 //
 // The binary always comes from a GitHub release: the one --relo-version names,
-// the one this package was published as when that is a prerelease, or the
-// latest release. Rerun this file by hand with the flag to install a specific
+// else the one this package was published as, so the binary and the shim stay
+// on one version. Rerun this file by hand with the flag to install a specific
 // release.
 import { spawnSync } from 'node:child_process';
 import { existsSync, readFileSync } from 'node:fs';
@@ -42,7 +42,7 @@ import {
 	warn
 } from './progress.mjs';
 import { target } from './platform.mjs';
-import { assets, checksumsUrl, prereleaseTag, selectBundle, tagFromArgs, url } from './release.mjs';
+import { assets, checksumsUrl, pinnedTag, selectBundle, tagFromArgs, url } from './release.mjs';
 import { extractBinary } from './archive.mjs';
 
 const packageRoot = resolve(dirname(fileURLToPath(import.meta.url)), '..');
@@ -146,7 +146,7 @@ async function fromRelease(tag, asset, startedAt) {
 
 try {
 	const startedAt = Date.now();
-	const tag = tagFromArgs(process.argv.slice(2)) ?? prereleaseTag(publishedVersion);
+	const tag = tagFromArgs(process.argv.slice(2)) ?? pinnedTag(publishedVersion);
 	const asset = target();
 	const { version } = assets(tag);
 	await openScreen(LOGO, 'I N S T A L L E R', [

package/lib/release.mjs

@@ -21,15 +21,15 @@ export function tagFromArgs(argv = []) {
 	return null;
 }
 
-// prereleaseTag pins an install to the version this package was published as,
-// and only when that version is a prerelease. A beta published under the beta
-// dist-tag would otherwise resolve "latest" and install the stable binary,
-// which is not the build its caller asked for. A stable package keeps
-// following the latest release, so re-publishing an old stable version still
-// tracks the channel instead of pinning itself.
-export function prereleaseTag(published) {
-	const pinned = version(published);
-	return pinned && /^\d+\.\d+\.\d+-/.test(pinned) ? pinned : null;
+// pinnedTag pins an install to the version this package was published as. npm
+// does not forward the install spec -- `@v0.1.8`, `@beta`, `@latest` -- to
+// lifecycle scripts, so the installed package version is the only pin the
+// postinstall can see. The publish job checks every declaration against the
+// release tag first, so a published version always has a matching v<version>
+// release to download: following the package keeps the binary and the shim on
+// one version instead of installing the latest binary under an older package.
+export function pinnedTag(published) {
+	return version(published);
 }
 
 // assets resolves the download directory for one release. Without a tag it

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@jonaskahn/relo",
-	"version": "0.1.9",
+	"version": "0.1.10",
 	"description": "One local proxy that lets Codex, Claude Code, Cursor and Grok, etc. Talk to any model, any provider with no config changes",
 	"license": "AGPL-3.0-only",
 	"type": "module",