From 48b485a8021da2c9249b483b5d37cbd8f07f7be6 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 21 May 2026 17:32:43 +0000
Subject: [PATCH] Release

---
 .changeset/add-graph-follow-lexicon.md            |  5 -----
 .changeset/clarify-knownvalues-open-vocabulary.md |  5 -----
 CHANGELOG.md                                      | 10 ++++++++++
 package-lock.json                                 |  4 ++--
 package.json                                      |  2 +-
 5 files changed, 13 insertions(+), 13 deletions(-)
 delete mode 100644 .changeset/add-graph-follow-lexicon.md
 delete mode 100644 .changeset/clarify-knownvalues-open-vocabulary.md

diff --git a/.changeset/add-graph-follow-lexicon.md b/.changeset/add-graph-follow-lexicon.md
deleted file mode 100644
index 5f86d742..00000000
--- a/.changeset/add-graph-follow-lexicon.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@hypercerts-org/lexicon": minor
----
-
-Add `app.certified.graph.follow` lexicon — a social-graph follow record schema-compatible with `app.bsky.graph.follow` (same `tid` key, same `subject` / `createdAt` / optional `via` strongRef fields). Exports new `GRAPH_FOLLOW_NSID`, `GRAPH_FOLLOW_LEXICON_JSON`, `GRAPH_FOLLOW_LEXICON_DOC`, and `AppCertifiedGraphFollow` type namespace.
diff --git a/.changeset/clarify-knownvalues-open-vocabulary.md b/.changeset/clarify-knownvalues-open-vocabulary.md
deleted file mode 100644
index 8ebb5d8e..00000000
--- a/.changeset/clarify-knownvalues-open-vocabulary.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@hypercerts-org/lexicon": patch
----
-
-Clarify that `knownValues` is an open vocabulary, not a closed enum. Adds a "Schema Conventions" section to README.md explaining that custom string values are permitted on any `knownValues` field (and contrasting with `enum`, which is closed and validator-enforced). Updates inline descriptions on `app.certified.location#locationType`, `org.hypercerts.workscope.tag#category`, and `org.hypercerts.workscope.tag#status` to explicitly note that values beyond the listed set are permitted — bringing them in line with the existing wording on `org.hypercerts.collection#type`, `org.hypercerts.context.attachment#contentType`, and `app.certified.badge.definition#badgeType`. The `locationType` description now also explicitly calls out that polygons / multipolygons / featurecollections use the catch-all `geojson` entry rather than a typed variant. Fixes a misleading line in STRING_CONSTRAINTS.md that conflated `knownValues` with `enum`. Documentation-only — no schema or type changes.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index e24bd3b4..8e09a6fa 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,15 @@
 # @hypercerts-org/lexicon
 
+## 0.13.0
+
+### Minor Changes
+
+- [#209](https://github.com/hypercerts-org/hypercerts-lexicon/pull/209) [`8ec051f`](https://github.com/hypercerts-org/hypercerts-lexicon/commit/8ec051faaf46b507409d97ca609b05fb8f318a3d) Thanks [@s-adamantine](https://github.com/s-adamantine)! - Add `app.certified.graph.follow` lexicon — a social-graph follow record schema-compatible with `app.bsky.graph.follow` (same `tid` key, same `subject` / `createdAt` / optional `via` strongRef fields). Exports new `GRAPH_FOLLOW_NSID`, `GRAPH_FOLLOW_LEXICON_JSON`, `GRAPH_FOLLOW_LEXICON_DOC`, and `AppCertifiedGraphFollow` type namespace.
+
+### Patch Changes
+
+- [#213](https://github.com/hypercerts-org/hypercerts-lexicon/pull/213) [`80e5b42`](https://github.com/hypercerts-org/hypercerts-lexicon/commit/80e5b427b1e6886417d2db12017e7aa4a42a6482) Thanks [@s-adamantine](https://github.com/s-adamantine)! - Clarify that `knownValues` is an open vocabulary, not a closed enum. Adds a "Schema Conventions" section to README.md explaining that custom string values are permitted on any `knownValues` field (and contrasting with `enum`, which is closed and validator-enforced). Updates inline descriptions on `app.certified.location#locationType`, `org.hypercerts.workscope.tag#category`, and `org.hypercerts.workscope.tag#status` to explicitly note that values beyond the listed set are permitted — bringing them in line with the existing wording on `org.hypercerts.collection#type`, `org.hypercerts.context.attachment#contentType`, and `app.certified.badge.definition#badgeType`. The `locationType` description now also explicitly calls out that polygons / multipolygons / featurecollections use the catch-all `geojson` entry rather than a typed variant. Fixes a misleading line in STRING_CONSTRAINTS.md that conflated `knownValues` with `enum`. Documentation-only — no schema or type changes.
+
 ## 0.12.0
 
 ### Minor Changes
diff --git a/package-lock.json b/package-lock.json
index f0079887..55fd20de 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "@hypercerts-org/lexicon",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@hypercerts-org/lexicon",
-      "version": "0.12.0",
+      "version": "0.13.0",
       "license": "MIT",
       "dependencies": {
         "@atproto/lexicon": "^0.6.0",
diff --git a/package.json b/package.json
index 3460ea83..e3911af3 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@hypercerts-org/lexicon",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "description": "ATProto lexicon definitions and TypeScript types for the Hypercerts protocol",
   "type": "module",
   "main": "./dist/index.cjs",