From 6c46d8e8e5e6ad46dd880b621a5d94150daca137 Mon Sep 17 00:00:00 2001 From: Implementer Date: Mon, 12 Oct 2026 18:45:53 +0200 Subject: [PATCH] Takes meta-model 0.94.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The upgrade moves the tooling in .companygraph/manifest.json and the instance check's workflow ref from 0.92.0 to 0.94.0 and the vendored core from 0.67.0 to 0.69.0. Core changes in one sentence of its conventions: R9 admits an enum type column for a ref → by row beside a string one, so a schema that can list the types a row may name has R8 hold them. No page of this instance changes, and no schema it vendors does; the release ships the requirements pack, which this instance does not take. Upstream notes are at https://github.com/companygraph/meta-model/releases/tag/v0.94.0. Verified: npx --yes 'github:companygraph/meta-model#v0.94.0' upgrade . ran, a second run found nothing to do, and check . passes; conventions-format, conventions-check and conventions-sync check pass. The agent pass over the writing rules was not run, since no page changed. Process: Delivery Phase: Implement Track: Code Co-Authored-By: Claude Fable 5.1 --- .companygraph/manifest.json | 8 ++++---- .github/workflows/companygraph.yml | 2 +- meta/core/CONVENTIONS.md | 2 +- meta/core/manifest.json | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/.companygraph/manifest.json b/.companygraph/manifest.json index 9a4fbea..efcd808 100644 --- a/.companygraph/manifest.json +++ b/.companygraph/manifest.json @@ -1,7 +1,7 @@ { - "tooling": "0.92.0", + "tooling": "0.94.0", "core": { - "version": "0.67.0", + "version": "0.69.0", "shape": 3, "source": "bundled" }, @@ -12,7 +12,7 @@ "meta" ], "files": { - "meta/core/CONVENTIONS.md": "sha256:2788ace5f67825b8ba19a7e6ca55418cb8244c8e53f6de645ca9d74685c48906", + "meta/core/CONVENTIONS.md": "sha256:dd5dfc1a23f67f800f17a36589ab7e5e060727c6a4e6212200381d9492b58eed", "meta/core/LICENSE": "sha256:cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30", "meta/core/achievement-kind-schema.md": "sha256:7697cbd987d7a5ca330341d62a3cee306f9c6bc9db81ed5b742b3d2b5c8a1fc2", "meta/core/brand-schema.md": "sha256:85a0d0cfcd2a6ba3dd89a4abafd82cf3e1adbda354e53b69f8088d5b191f59ec", @@ -30,7 +30,7 @@ "meta/core/identity-schema.md": "sha256:d53b1414f6c457374d8af800a5bc832ae80bb839446d334c7060dd1eea0bed30", "meta/core/kpi-schema.md": "sha256:518e260893a012028855a5e82cb33b93c17171b254107428fb69d99b77a8fff0", "meta/core/localization-schema.md": "sha256:6d5ef97f36d10b4bde890c52d97a01c19d1529c3fb92956ed26a0dab9eb0950a", - "meta/core/manifest.json": "sha256:9ad604cd1a6a8def1e01460208bea67e21642cac97addfc7574202130cb108b9", + "meta/core/manifest.json": "sha256:897ddd5a1c8b04ffd14e0bd6c91e874ba8da9644d768d4d84cb0b83dc5f47214", "meta/core/phase-schema.md": "sha256:e1b5adcc33360c2a5081e919b18ae8166f3f04e53d83f55a77c2158af3f60d9c", "meta/core/process-schema.md": "sha256:65a8ee2446a97455e77d2640634686e94969a895c0b5d4d7237f77dcd7a5bf27", "meta/core/processing-activity-schema.md": "sha256:6d8d18b2ae1e2b97d6685ee4c88141b963df679a3f418ed125945b8ae6208243", diff --git a/.github/workflows/companygraph.yml b/.github/workflows/companygraph.yml index fea24b3..00fb6de 100644 --- a/.github/workflows/companygraph.yml +++ b/.github/workflows/companygraph.yml @@ -5,4 +5,4 @@ on: pull_request: jobs: companygraph: - uses: companygraph/meta-model/.github/workflows/instance-check.yml@v0.92.0 + uses: companygraph/meta-model/.github/workflows/instance-check.yml@v0.94.0 diff --git a/meta/core/CONVENTIONS.md b/meta/core/CONVENTIONS.md index 92f890c..b013bea 100644 --- a/meta/core/CONVENTIONS.md +++ b/meta/core/CONVENTIONS.md @@ -120,7 +120,7 @@ Some fields name a thing that is sometimes an entity and sometimes not — an em The `?` is not `Required`, though the two read as one thing on a first pass. `Required` says whether the field may be absent; `ref?` says whether a value that is present must resolve. A field can be both, and `organization` is. -Some tables name entities of more than one type, as a question names whatever its answer rests on. `ref → by ` is how a schema says so: each cell names an entity of the type the same row's `` cell names, written as the type's schema file is named without `-schema.md`. Where that type may be owned, `ref → by in ` reads the owner from the row's `` cell, filled exactly where the type is owned (R4, R10). The form is a column's only, because a frontmatter field and a heading have no row to read a type from, and the columns it names are `string` columns of the same table, whose names do not contain the word `in`. +Some tables name entities of more than one type, as a question names whatever its answer rests on. `ref → by ` is how a schema says so: each cell names an entity of the type the same row's `` cell names, written as the type's schema file is named without `-schema.md`. Where that type may be owned, `ref → by in ` reads the owner from the row's `` cell, filled exactly where the type is owned (R4, R10). The form is a column's only, because a frontmatter field and a heading have no row to read a type from, and the columns it names are `string` or `enum` columns of the same table, whose names do not contain the word `in`: the type column an `enum` where the schema can list the types a row may name, so that a type off the list is R8's, and a `string` where it cannot, and the owner column a `string`. A required list that is present and empty is absent in every sense that matters: nothing resolves, no edge is drawn, and the page reads as though it had answered a question it did not. So a required field typed `array` or `array of ref → ` carries at least one entry. An optional list written empty is how an author says none yet, and that is theirs to say, since the field could have been left out. diff --git a/meta/core/manifest.json b/meta/core/manifest.json index 262f883..3e75c27 100644 --- a/meta/core/manifest.json +++ b/meta/core/manifest.json @@ -1 +1 @@ -{ "version": "0.67.0", "shape": 3 } +{ "version": "0.69.0", "shape": 3 }