Standard → Version model, Changesets releasing, and standards-checker 1.2.0-beta.2

Each OGC standard — JSON-FG and OGC API Features / Processes / Records — is
now a first-class Standard owning an explicit version, driven by a single
Standard[] config for both the web app and the CLI (--standard/--version;
--ruleset stays as a deprecated alias, legacy URLs redirect). Releases move
to Changesets, CI gains the pnpm dedupe --check guard, and the
@geonovum/standards-checker dependency is pinned to 1.2.0-beta.2 from the
registry.

Author: joostfarla

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets).
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md).

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.4/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

.changeset/multi-version-standards.md

@@ -0,0 +1,15 @@
+---
+"@geonovum/ogc-checker": minor
+---
+
+Adopt the **Standard → Version** model from `@geonovum/standards-checker`.
+
+Each OGC standard — JSON-FG and OGC API Features / Processes / Records — is now a first-class
+`Standard` that owns an explicit version, rather than a bare ruleset slug. A single `Standard[]`
+config drives both the web app and the CLI.
+
+- **CLI:** validate with `--standard <slug>` and optional `--version <id>` (default = the latest
+  `final` version). The old `--ruleset <slug>` flag keeps working as a **deprecated** alias that
+  warns on stderr and resolves to the equivalent standard/version.
+- **UI:** the header gains a standard selector and an always-visible version selector; the URL anchor
+  is `/#/{standard}/{version}` and legacy single-slug URLs redirect to it.

.github/workflows/build.yml

@@ -23,6 +23,7 @@ jobs:
           node-version: ${{ matrix.node-version }}
           cache: 'pnpm'
       - run: pnpm install --frozen-lockfile
+      - run: pnpm dedupe --check
       - run: pnpm build
       - run: pnpm lint
       - run: pnpm test run

.github/workflows/publish.yml

@@ -37,6 +37,7 @@ jobs:
             exit 1
           fi
       - run: pnpm install --frozen-lockfile
+      - run: pnpm dedupe --check
       - run: pnpm build
       - run: |
           VERSION=$(node -p "require('./package.json').version")

README.md

@@ -6,6 +6,8 @@ Validates JSON-FG documents and OGC API endpoints against OGC specifications.
 
 Built on [`@geonovum/standards-checker`](https://github.com/Geonovum/standards-checker); see its documentation for the validation engine, CLI toolkit, and web UI framework.
 
+Release notes are in [`CHANGELOG.md`](CHANGELOG.md); see [Versioning & releasing](#versioning--releasing) for how it is produced.
+
 **Demo:** https://geonovum.github.io/ogc-checker/
 
 ## CLI
@@ -14,45 +16,62 @@ Built on [`@geonovum/standards-checker`](https://github.com/Geonovum/standards-c
 
 ```bash
 # From a local file
-npx @geonovum/ogc-checker@latest validate --ruleset json-fg --input ./data/spec.json
+npx @geonovum/ogc-checker@latest validate --standard json-fg --input ./data/spec.json
 
 # From a URL
-npx @geonovum/ogc-checker@latest validate --ruleset json-fg --input https://example.com/spec.json
+npx @geonovum/ogc-checker@latest validate --standard json-fg --input https://example.com/spec.json
 
 # From stdin
-cat spec.json | npx @geonovum/ogc-checker@latest validate --ruleset json-fg
+cat spec.json | npx @geonovum/ogc-checker@latest validate --standard json-fg
 ```
 
 ### Install globally
 
 ```bash
 npm install -g @geonovum/ogc-checker@latest
-ogc-checker validate --ruleset json-fg --input ./data/spec.json
+ogc-checker validate --standard json-fg --input ./data/spec.json
 ```
 
 ### From a local clone
 
 ```bash
 pnpm install
 pnpm build:cli
-node dist/cli.mjs validate --ruleset json-fg --input ./data/spec.json
+node dist/cli.mjs validate --standard json-fg --input ./data/spec.json
 ```
 
-Available rulesets: `json-fg`, `ogc-api-features`, `ogc-api-processes`, `ogc-api-records`.
+Available standards: `json-fg`, `ogc-api-features`, `ogc-api-processes`, `ogc-api-records`. Each currently
+ships a single version, so `--version` is optional and defaults to it (`ogc-api-processes` is `2.0`, a draft).
+
+The old `--ruleset <slug>` flag still works as a **deprecated** alias (it prints a warning on stderr and
+resolves the old slug to the same standard/version): `--ruleset json-fg` == `--standard json-fg --version 1.0`.
 
 ### CLI flags
 
-| Flag                | Description                               | Default      |
-| ------------------- | ----------------------------------------- | ------------ |
-| `--ruleset <name>`  | Ruleset to run (listed in `--help`)       | _(required)_ |
-| `--input <file\|->` | Input file, URL, or `-` for stdin         | `-`          |
-| `--format <fmt>`    | Output: `table`, `json`                   | `table`      |
-| `--fail-on <level>` | Exit code policy: `none`, `warn`, `error` | `error`      |
+| Flag                | Description                                       | Default            |
+| ------------------- | ------------------------------------------------- | ------------------ |
+| `--standard <slug>` | Standard to validate against                      | _(required)_       |
+| `--version <id>`    | Version of the standard                           | latest final       |
+| `--ruleset <slug>`  | **Deprecated** alias for `--standard`/`--version` | —                  |
+| `--input <file\|->` | Input file, URL, or `-` for stdin                 | `-`                |
+| `--format <fmt>`    | Output: `table`, `json`                           | `table`            |
+| `--fail-on <level>` | Exit code policy: `none`, `warn`, `error`         | `error`            |
 
 Exit codes: `0` = pass, `1` = failed per `--fail-on` policy, `>1` = unexpected error.
 
 ## Specifications
 
+Each specification below maps to a **standard** in the checker; its requirement table lists the
+conformance classes of that standard's current version. Pick the standard in the header, then the
+version:
+
+| Standard (`--standard`) | Version (`--version`) | Status | Covers                                                    |
+| ----------------------- | --------------------- | ------ | --------------------------------------------------------- |
+| `json-fg`               | `1.0.0`               | final  | JSON-FG                                                   |
+| `ogc-api-features`      | `1.0.1`               | final  | OGC API - Features Part 1 (Core) and Part 2 (CRS by ref.) |
+| `ogc-api-processes`     | `2.0.0`               | draft  | OGC API - Processes Part 1 (Core)                         |
+| `ogc-api-records`       | `1.0.0`               | final  | OGC API - Records Part 1 (Core)                           |
+
 ### JSON-FG
 
 Version: 1.0.0 — [Specification](https://docs.ogc.org/is/21-045r1/21-045r1.html)
@@ -277,19 +296,25 @@ pnpm install
 Run a single test file:
 
 ```bash
-npx vitest run src/specs/json-fg/rulesets/core.test.ts
+npx vitest run src/standards/json-fg/rulesets/core.test.ts
 ```
 
-### Publishing
+### Versioning & releasing
 
-Published to npm automatically when a version tag is pushed:
+Versioning, the changelog, and publishing are driven by [Changesets](https://changesets.dev/). Describing a change is decoupled from cutting a release:
 
-```bash
-git tag v1.0.0
-git push --tags
-```
+1. **Add a changeset with your change.** Run `pnpm changeset`, pick the bump (`major` / `minor` / `patch`), and write a one-line summary. This creates a `.changeset/<name>.md` file — commit it with your PR. Omit only for changes that don't affect the published package (CI, internal docs, tests).
+
+2. **Cut the release.** Run `pnpm version-packages` (alias for `changeset version`). It consumes the pending `.changeset/*.md` files, bumps `package.json`, and prepends the summaries to `CHANGELOG.md`. Review and commit the result. Don't hand-edit the `version` field — Changesets owns it.
+
+3. **Publish.** Tag the released version and push; the CI workflow verifies `package.json` matches the tag, builds, tests, publishes to npm, and deploys to GitHub Pages:
+
+   ```bash
+   git tag v1.1.0
+   git push --tags
+   ```
 
-This triggers the CI workflow that builds, tests, publishes to npm, and deploys to GitHub Pages.
+   `pnpm release` (`pnpm build && changeset publish`) publishes to npm locally if you need to bypass the workflow (it does not deploy Pages).
 
 ## License
 

package.json

@@ -27,18 +27,22 @@
     "lint": "eslint .",
     "lint:fix": "eslint . --fix",
     "preview": "vite preview",
-    "test": "vitest"
+    "test": "vitest",
+    "changeset": "changeset",
+    "version-packages": "changeset version",
+    "release": "pnpm build && changeset publish"
   },
   "prettier": "@geonovum/standards-checker/prettier",
   "dependencies": {
-    "@geonovum/standards-checker": "^1.1.4",
+    "@geonovum/standards-checker": "1.2.0-beta.2",
     "luxon": "^3.7.2",
     "ramda": "^0.32.0",
     "react": "^19.2.7",
     "react-dom": "^19.2.7",
     "react-router-dom": "^7.18.1"
   },
   "devDependencies": {
+    "@changesets/cli": "^2.31.0",
     "@types/luxon": "^3.7.2",
     "@types/ramda": "^0.32.0",
     "esbuild": "^0.28.1",