Skip to content

Beautiful, AI-native markdown IDE and LLM wiki

docs(ok): retire "legacy" naming for the public release repo (PRD-7933) (#2947)

Andrew Mikofalvyaf4a806ec6da
diff --git a/.github/workflows/desktop-release.yml b/.github/workflows/desktop-release.yml
index c14cdb26c..ad0c8bc91 100644
--- a/.github/workflows/desktop-release.yml
+++ b/.github/workflows/desktop-release.yml
@@ -187,8 +187,8 @@ jobs:
# Detect channel from the release TAG (not package.json#version). Under
# the zero-commit-bump cadence (release.yml header lines 7-10), the
- # tag is the only source of truth for the release's version — legacy
- # commits at the tagged SHA carry the cycle-base version (e.g.
+ # tag is the only source of truth for the release's version — the
+ # public repo's commits at the tagged SHA carry the cycle-base version (e.g.
# `0.5.0-beta.5`), not the tag's version. Tag also drives manifest
# selection (beta-* vs latest-* channel files) for the stable-promotion
# case where tag (`v0.4.0`) and on-disk package.json (`0.4.0-beta.N`)
diff --git a/.github/workflows/promote-stable.yml b/.github/workflows/promote-stable.yml
index 046337d97..bb6726c5a 100644
--- a/.github/workflows/promote-stable.yml
+++ b/.github/workflows/promote-stable.yml
@@ -19,8 +19,8 @@ name: Promote stable
# 3. Tags vX.Y.Z (no suffix) at the SAME SHA as the beta tag.
# 4. Creates a non-prerelease GitHub Release at vX.Y.Z as a DRAFT.
# desktop-release.yml fires automatically and builds the stable DMG with
-# --config.extraMetadata.version=X.Y.Z (override since the legacy commit
-# still has -beta.N in package.json).
+# --config.extraMetadata.version=X.Y.Z (override since the public repo's
+# commit still has -beta.N in package.json).
# 5. desktop-release.yml smokes that DMG, promotes the draft to published,
# and only then dispatches publish-stable to release.yml, which promotes
# the npm `latest` dist-tag using a transient package.json#version
@@ -44,7 +44,7 @@ name: Promote stable
# manually (two-button fallback).
#
# Concurrency group is shared with release.yml so beta cuts and stable
-# promotions never race on the same legacy state.
+# promotions never race on the same public-repo state.
#
# Token model. We mint a GitHub App installation token via
# actions/create-github-app-token for every identity-asserting call. The
@@ -220,7 +220,7 @@ jobs:
# actions/checkout fetches all refs with fetch-depth: 0; verify
# the resolved tag is present.
if ! git rev-parse "refs/tags/${BETA_TAG}" >/dev/null 2>&1; then
- echo "::error::Beta tag '${BETA_TAG}' not found on legacy. Did the auto-cadence release run?"
+ echo "::error::Beta tag '${BETA_TAG}' not found on the public repo. Did the auto-cadence release run?"
exit 1
fi
echo "Tag ${BETA_TAG} resolves to $(git rev-parse "refs/tags/${BETA_TAG}")"
@@ -472,10 +472,11 @@ jobs:
if: steps.ver.outputs.skip != 'true'
# Auto-triggering main-reset.yml on agents-private needs a credential
# with write access to THAT repo; the workflow-default GITHUB_TOKEN is
- # scoped to legacy only and cannot dispatch cross-repo. The "Inkeep OK
- # Release Bridge" GitHub App supplies it: installed on agents-private,
- # its App-ID + private key live in legacy's secrets, and the next step
- # mints a short-lived installation token at runtime (no static
+ # scoped to the public repo only and cannot dispatch cross-repo. The
+ # "Inkeep OK Release Bridge" GitHub App supplies it: installed on
+ # agents-private, its App-ID + private key live in the public repo's
+ # secrets, and the next step mints a short-lived installation token
+ # at runtime (no static
# long-lived token stored). If the App secrets are absent the bridge
# is not configured — skip silently and promotion stays two-button
# (engineer runs main-reset.yml manually). Secrets cannot be read in
@@ -501,8 +502,8 @@ jobs:
# Public client ID for inkeep-ok-release-bridge (non-secret; supersedes the deprecated app-id input).
client-id: Iv23lii4qS2FAc6tkzfI
private-key: ${{ secrets.OK_RELEASE_BRIDGE_APP_PRIVATE_KEY }}
- # The bridge App is installed on agents-private, not on legacy
- # (where this workflow runs). owner + repositories scope the minted
+ # The bridge App is installed on agents-private, not on the public
+ # repo (where this workflow runs). owner + repositories scope the minted
# token to that cross-repo installation.
owner: inkeep
repositories: agents-private
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index eca4d4d7e..fc27f95e1 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -3,12 +3,13 @@ name: Release
# Release workflow on inkeep/open-knowledge. Single npm publisher
# for BOTH auto-cadence beta releases AND on-demand stable promotions.
#
-# Beta path: event-driven on `push` to legacy/main with a paths filter on
-# `.changeset/**`. Copybara mirrors `public/open-knowledge/.changeset/*.md`,
-# `pre.json`, and `config.json` from agents-private. When agents-private
-# merges a PR with a changeset, Copybara batches it into a Project-import
-# commit on legacy/main; that import push IS the release trigger. The
-# workflow then runs `compute-next-beta.mjs` locally to derive baseVersion
+# Beta path: event-driven on `push` to open-knowledge/main with a paths
+# filter on `.changeset/**`. Copybara mirrors
+# `public/open-knowledge/.changeset/*.md`, `pre.json`, and `config.json`
+# from agents-private. When agents-private merges a PR with a changeset,
+# Copybara batches it into a Project-import commit on open-knowledge/main;
+# that import push IS the release trigger. The workflow then runs
+# `compute-next-beta.mjs` locally to derive baseVersion
# + release notes from the pending changeset pile (skip-gated by the
# previous beta's embedded consumed-set marker), resolves -beta.N inside
# the ok-release-cadence concurrency slot, and tags `github.sha` —
@@ -16,7 +17,7 @@ name: Release
# happens AT the push event. This replaces the prior cross-repo
# repository_dispatch model, which suffered an off-by-one: the dispatch
# from agents-private fired before Copybara's mirror push landed, so
-# legacy/main HEAD was still the previous import when checkout resolved
+# open-knowledge/main HEAD was still the previous import when checkout resolved
# `github.sha`, tagging the wrong commit (Linear PRD-6701).
#
# Three trigger types:
@@ -56,7 +57,7 @@ name: Release
# - Checks out the stable tag (= the same SHA as the corresponding
# beta tag).
# - Overrides every fixed-group package.json#version to the clean
-# X.Y.Z (the legacy commit at that SHA carries whatever
+# X.Y.Z (the public repo's commit at that SHA carries whatever
# agents-private mirrored, which is a `0.0.0` placeholder under
# the zero-commit-bump cadence).
# - Publishes @inkeep/[email protected] to npm with
@@ -87,7 +88,7 @@ name: Release
# event-driven betas and promote-stable route their npm publishes here.
#
# Concurrency group is shared with promote-stable.yml so beta cuts and
-# stable promotions never race on the same legacy state.
+# stable promotions never race on the same public-repo state.
on:
push:
@@ -369,7 +370,7 @@ jobs:
# concurrent push events (e.g., two rapid Copybara imports that each
# carry a changeset) see different N's and never collide on tag
# creation. The concurrency group serializes runs against the same
- # legacy state, so the max-N scan is race-free.
+ # public-repo state, so the max-N scan is race-free.
- name: Resolve -beta.N counter
if: steps.compute-beta.outputs.run_beta == 'true'
id: resolve-beta
@@ -531,7 +532,7 @@ jobs:
fi
# Same transient-jq primitive as the beta path: edit
- # version fields in place, never commit. The legacy commit at
+ # version fields in place, never commit. The public repo's commit at
# the source beta SHA carries whatever package.json version
# agents-private mirrored (under the zero-commit-bump cadence,
# that's the placeholder version on main); we override to the
diff --git a/scripts/compute-next-beta.mjs b/scripts/compute-next-beta.mjs
index 9799f74f3..a85beaccb 100644
--- a/scripts/compute-next-beta.mjs
+++ b/scripts/compute-next-beta.mjs
@@ -27,7 +27,7 @@
* embedded consumed-set marker for the next cut to read.
* 8. Read the bumped package.json#version to derive baseVersion + maxBumpType.
*
- * Emits JSON to stdout (legacy beta-cut workflow contract):
+ * Emits JSON to stdout (public-repo beta-cut workflow contract):
* { skip: false, baseVersion: "X.Y.Z", maxBumpType: "patch"|"minor",
* pendingCount: N, releaseNotes: "...markdown..." }
* or, when no new changesets are pending:
@@ -351,7 +351,7 @@ function main() {
}
// Compute maxBumpType across the WHOLE cycle (delta + prior). baseVersion
- // ships to legacy and must reflect the cycle's eventual stable target — a
+ // ships to the public repo and must reflect the cycle's eventual stable target — a
// delta-only patch on a cycle that already accumulated a minor would
// otherwise emit the wrong base.
const cycleBumpTypes = allIds.map((id) =>