@toist/spec 0.8.0 → 0.8.2

package/CHANGELOG.md

@@ -2,6 +2,24 @@
 
 All notable changes to `@toist/spec` are recorded here.
 
+## 0.8.2 — 2026-05-08
+
+- **Pipeline `apiVersion` canonical literal renamed** from `"2121.fi/v1"`
+  to `"toist.in/v1"`. The legacy literal is still accepted with a
+  deprecation warning (`apiVersion "2121.fi/v1" is deprecated; use
+  "toist.in/v1" instead`). Existing pipelines keep working; the warning
+  tells authors what to update. Will eventually become a hard error.
+- Generated JSON Schema `$id` updated to
+  `https://toist.in/schemas/pipeline-v1.json` and the schema title to
+  `Pipeline (toist.in/v1)`.
+- Aligns with the `@toist/*` npm scope, the `/manifest` schema URL
+  shipped in v0.8.0 (`https://toist.in/schemas/manifest-v1.json`), and
+  the public website.
+
+## 0.8.1 — 2026-05-08
+
+Lockstep version bump. No functional changes in this package.
+
 ## 0.8.0 — 2026-05-08
 
 - **Structural `DataHandle` / `DataStatement` interfaces** replace the

package/README.md

@@ -6,7 +6,7 @@ Pure Toist pipeline-format tooling: YAML parsing, discriminator/expression parsi
 import { parseYaml, validateSpec } from "@toist/spec"
 
 const spec = parseYaml(`
-apiVersion: "2121.fi/v1"
+apiVersion: "toist.in/v1"
 id: hello
 nodes:
   - id: greet

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@toist/spec",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "type": "module",
   "main": "./src/index.ts",
   "types": "./src/index.ts",

package/src/jsonschema.ts

@@ -9,7 +9,7 @@
 
 import type { ParamDef, PortDef, NodeKindManifest, ResourceTypeDef } from "./kinds.ts"
 
-const API_VERSION = "2121.fi/v1"
+const API_VERSION = "toist.in/v1"
 const SLUG_PATTERN = "^[A-Za-z][\\w-]*$"
 
 export type JsonSchema = Record<string, unknown>
@@ -185,8 +185,8 @@ export function pipelineSchema(kinds: NodeKindManifest[]): JsonSchema {
 
   return {
     $schema:     "https://json-schema.org/draft/2020-12/schema",
-    $id:         `https://2121.fi/pipeline-spec/v1/pipeline.schema.json`,
-    title:       "Pipeline (2121.fi/v1)",
+    $id:         `https://toist.in/schemas/pipeline-v1.json`,
+    title:       "Pipeline (toist.in/v1)",
     description: "Generated from the live kind manifest. Regenerate when kinds are added or changed.",
     type:        "object",
     properties: {

package/src/validate.ts

@@ -92,7 +92,14 @@ export interface ValidateResult {
 // ─── Closed sets and constants ───────────────────────────────────────────────
 
 const SLUG_RE = /^[A-Za-z][\w-]*$/
-const API_VERSION = "2121.fi/v1"
+
+// v0.8.2 renamed the spec authority from `2121.fi` (the company) to
+// `toist.in` (the public product). Both literals are accepted; the
+// legacy form emits a deprecation warning and rewrites to the canonical
+// form on the parsed spec. Will eventually become a hard error — give
+// it a major bump's worth of grace first.
+const API_VERSION = "toist.in/v1"
+const API_VERSION_LEGACY = "2121.fi/v1"
 
 const ALLOWED_PIPELINE_KEYS = new Set([
   "apiVersion", "id", "label", "description", "schedule", "payloadSchema", "nodes",
@@ -147,13 +154,17 @@ export function validateSpec(input: unknown, options: ValidateOptions = {}): Val
     }
   }
 
-  // §13.4 — apiVersion. Implicit-v1 with warning per §7.
+  // §13.4 — apiVersion. Implicit-v1 with warning per §7. Two accepted
+  // literals: "toist.in/v1" (canonical) and "2121.fi/v1" (legacy, warned).
   let apiVersion: string
   if (spec.apiVersion === undefined) {
     warnings.push(`apiVersion absent; treating as "${API_VERSION}". Add apiVersion: "${API_VERSION}" explicitly.`)
     apiVersion = API_VERSION
   } else if (spec.apiVersion === API_VERSION) {
     apiVersion = API_VERSION
+  } else if (spec.apiVersion === API_VERSION_LEGACY) {
+    warnings.push(`apiVersion "${API_VERSION_LEGACY}" is deprecated; use "${API_VERSION}" instead.`)
+    apiVersion = API_VERSION
   } else {
     errors.push(`unsupported apiVersion: ${JSON.stringify(spec.apiVersion)} (this runner accepts "${API_VERSION}")`)
     apiVersion = API_VERSION