@linxiraos/pi-utils 1.3.2 → 1.4.0

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 ## [Unreleased]
 
+## [1.4.0] - 2026-10-21
+
+- Version line moves to 1.4.0 with the rest of the suite; no user-visible change in this package.
+
 ## [1.3.2] - 2026-10-19
 
 - Version line moves to 1.3.2 with the rest of the suite; no user-visible change in this package.

package/dist/types/release-assets.d.ts

@@ -16,6 +16,25 @@
  * assets are `<prefix><os>[-musl]-<arch>[.exe]`.
  */
 export declare const RELEASE_CLI_ASSET_PREFIX = "zeta-cli-";
+/**
+ * CLI assets a release actually publishes — the `release_binary` matrix in
+ * `.github/workflows/ci.yml`. The build script can still produce a darwin or
+ * arm64 leg (`scripts/ci-release-build-binaries.ts` keeps those targets
+ * buildable), but a leg the matrix does not build has no asset: the updater
+ * must never compute its name, or `zetacode update` downloads a 404.
+ *
+ * `scripts/check-release-asset-names.ts` holds this set equal to the matrix's
+ * `binary_path` basenames, so a platform trim updates one list.
+ */
+export declare const SHIPPED_CLI_ASSETS: readonly string[];
+/**
+ * {@link releaseCliAssetName} restricted to the shipped matrix: undefined means
+ * this host has no standalone binary release, so the caller must not build a
+ * download URL at all.
+ */
+export declare function shippedCliAssetName(platform: NodeJS.Platform, arch: string, options?: {
+    musl?: boolean;
+}): string | undefined;
 /** Release asset for a CLI binary, e.g. `zeta-cli-windows-x64.exe`. */
 export declare function releaseCliAssetName(platform: NodeJS.Platform, arch: string, options?: {
     musl?: boolean;

package/dist/types/yaml-config.d.ts

@@ -1,2 +1,9 @@
+/**
+ * Resolve a canonical `.yml` config path for reading: the canonical path wins
+ * when it exists, otherwise a present `.yaml` sibling is used. Writes must keep
+ * targeting the canonical path — the sibling is a read-only compatibility
+ * fallback, matching `ConfigFile`.
+ */
+export declare function resolveYamlConfigReadPath(canonicalPath: string): string;
 /** Serialize config YAML without Bun's trailing space on block mapping headers. */
 export declare function stringifyYamlConfig(value: unknown): string;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@linxiraos/pi-utils",
-	"version": "1.3.2",
+	"version": "1.4.0",
 	"description": "Shared utilities for pi packages",
 	"keywords": [
 		"utilities",
@@ -54,7 +54,7 @@
 		"fmt": "oxfmt --no-error-on-unmatched-pattern 'src/**/*.{ts,tsx}' '{test,bench,examples,scripts}/**/*.ts' '*.ts'"
 	},
 	"dependencies": {
-		"@linxiraos/pi-natives": "1.3.2"
+		"@linxiraos/pi-natives": "1.4.0"
 	},
 	"devDependencies": {
 		"@types/bun": "1.4.3"

package/src/release-assets.ts

@@ -27,6 +27,41 @@ const RELEASE_OS: Partial<Record<NodeJS.Platform, string>> = {
 
 const RELEASE_ARCH: Record<string, string> = { x64: "x64", arm64: "arm64" };
 
+/**
+ * CLI assets a release actually publishes — the `release_binary` matrix in
+ * `.github/workflows/ci.yml`. The build script can still produce a darwin or
+ * arm64 leg (`scripts/ci-release-build-binaries.ts` keeps those targets
+ * buildable), but a leg the matrix does not build has no asset: the updater
+ * must never compute its name, or `zetacode update` downloads a 404.
+ *
+ * `scripts/check-release-asset-names.ts` holds this set equal to the matrix's
+ * `binary_path` basenames, so a platform trim updates one list.
+ */
+export const SHIPPED_CLI_ASSETS: readonly string[] = [
+	"zeta-cli-linux-x64",
+	"zeta-cli-linux-musl-x64",
+	"zeta-cli-windows-x64.exe",
+];
+
+/**
+ * {@link releaseCliAssetName} restricted to the shipped matrix: undefined means
+ * this host has no standalone binary release, so the caller must not build a
+ * download URL at all.
+ */
+export function shippedCliAssetName(
+	platform: NodeJS.Platform,
+	arch: string,
+	options: { musl?: boolean } = {},
+): string | undefined {
+	let name: string;
+	try {
+		name = releaseCliAssetName(platform, arch, options);
+	} catch {
+		return undefined;
+	}
+	return SHIPPED_CLI_ASSETS.includes(name) ? name : undefined;
+}
+
 /** Release asset for a CLI binary, e.g. `zeta-cli-windows-x64.exe`. */
 export function releaseCliAssetName(platform: NodeJS.Platform, arch: string, options: { musl?: boolean } = {}): string {
 	const os = RELEASE_OS[platform];

package/src/yaml-config.ts

@@ -1,7 +1,20 @@
+import { existsSync } from "node:fs";
 import { YAML } from "bun";
 
 const YAML_MAPPING_HEADER_TRAILING_SPACE = /: +$/gm;
 
+/**
+ * Resolve a canonical `.yml` config path for reading: the canonical path wins
+ * when it exists, otherwise a present `.yaml` sibling is used. Writes must keep
+ * targeting the canonical path — the sibling is a read-only compatibility
+ * fallback, matching `ConfigFile`.
+ */
+export function resolveYamlConfigReadPath(canonicalPath: string): string {
+	if (!canonicalPath.endsWith(".yml")) return canonicalPath;
+	const sibling = `${canonicalPath.slice(0, -4)}.yaml`;
+	return existsSync(canonicalPath) || !existsSync(sibling) ? canonicalPath : sibling;
+}
+
 /** Serialize config YAML without Bun's trailing space on block mapping headers. */
 export function stringifyYamlConfig(value: unknown): string {
 	return YAML.stringify(value, null, 2).replace(YAML_MAPPING_HEADER_TRAILING_SPACE, ":");