From 22e4d9c3e33ff4306b2b5cc567032f9b78ee67f2 Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Wed, 22 Jul 2026 19:39:34 +0200 Subject: [PATCH 1/2] docs(oci): make the wasm.directory registration step concrete The registration path was described vaguely ("add the namespace mapping to the wasm.directory registry config"). It is actually a GitHub issue on the index repo (yoshuawuyts/wasm): open the `registry-entry` template with kind=component / namespace=pulseengine / package=falcon-flight / repository=falcon-flight, which auto-opens a PR adding registry/pulseengine.toml. A new namespace is flagged for maintainer review, so the ghcr package must already exist and be public first. Documents the exact issue fields and the resulting toml so the org owner can follow it without re-deriving the mechanism. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG --- docs/OCI-DISTRIBUTION.md | 36 +++++++++++++++++++++++++++++------- 1 file changed, 29 insertions(+), 7 deletions(-) diff --git a/docs/OCI-DISTRIBUTION.md b/docs/OCI-DISTRIBUTION.md index 23e0dd9..a91f7c2 100644 --- a/docs/OCI-DISTRIBUTION.md +++ b/docs/OCI-DISTRIBUTION.md @@ -39,13 +39,35 @@ cosign verify ghcr.io/pulseengine/falcon-flight:1.127.0 \ tagged release populates it, in the org's package settings set `pulseengine/falcon-flight` visibility to **public** and link it to the `relay` repo. (One-time; subsequent pushes inherit the setting.) -2. **Register the namespace with wasm.directory.** Per its publishing guide, - add the `pulseengine` namespace → `ghcr.io` mapping to the wasm.directory - registry config (or your account's namespace list), then it indexes the - package. wasm.directory is **alpha** ("indexed data may be incomplete or - reset without notice; don't depend on it in production") — treat the listing - as a visibility channel, not a dependency. The durable, signed artifacts - remain the GitHub Release and the ghcr OCI ref. +2. **Register the namespace with wasm.directory.** Registration is a GitHub + issue on the index repo (`yoshuawuyts/wasm`), *not* a config file you push. + Open its **`registry-entry`** issue template with: + + - **kind**: `component` + - **namespace**: `pulseengine` + - **package name**: `falcon-flight` + - **repository**: `falcon-flight` + + Submitting it auto-opens a PR adding `registry/pulseengine.toml`: + + ```toml + [namespace] + name = "pulseengine" + registry = "ghcr.io/pulseengine" + + [[component]] + name = "falcon-flight" + repository = "falcon-flight" + ``` + + A **new namespace** is flagged for maintainer review, so the ghcr package must + already exist and be **public** (step 1) before submitting — an unpullable + entry is rejected. Do this only after a real release has populated the package. + + wasm.directory is **alpha** ("indexed data may be incomplete or reset without + notice; don't depend on it in production") — treat the listing as a visibility + channel, not a dependency. The durable, signed artifacts remain the GitHub + Release and the ghcr OCI ref. ## Scope note From cf9e3794dabbc7e3c30f5560f11836932ad68c09 Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Thu, 23 Jul 2026 07:14:18 +0200 Subject: [PATCH 2/2] docs(oci): correct wasm.directory repo + add the component-cli tool path MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reviewer caught it: the index repo is `yoshuawuyts/wasm.directory` (the `wasm`/`component-registry` names redirect to it), not `yoshuawuyts/wasm`. Also document the intended tool path — `component registry publish` prefills the registry-entry issue from a wasm.toml `[package]` — and make explicit that pushing the bytes (wkg oci push) and indexing in the meta-registry are two separate steps. Add the `OCI registry (new namespaces only)` field and a status note pointing at the actual filed issue #466 / auto-PR #467. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG --- docs/OCI-DISTRIBUTION.md | 31 +++++++++++++++++++++++-------- 1 file changed, 23 insertions(+), 8 deletions(-) diff --git a/docs/OCI-DISTRIBUTION.md b/docs/OCI-DISTRIBUTION.md index a91f7c2..d941de8 100644 --- a/docs/OCI-DISTRIBUTION.md +++ b/docs/OCI-DISTRIBUTION.md @@ -39,14 +39,24 @@ cosign verify ghcr.io/pulseengine/falcon-flight:1.127.0 \ tagged release populates it, in the org's package settings set `pulseengine/falcon-flight` visibility to **public** and link it to the `relay` repo. (One-time; subsequent pushes inherit the setting.) -2. **Register the namespace with wasm.directory.** Registration is a GitHub - issue on the index repo (`yoshuawuyts/wasm`), *not* a config file you push. - Open its **`registry-entry`** issue template with: - - - **kind**: `component` - - **namespace**: `pulseengine` - - **package name**: `falcon-flight` - - **repository**: `falcon-flight` +2. **Register the namespace with wasm.directory.** Publishing the bytes (the + `wkg oci push` above) and *indexing* in the meta-registry are two separate + steps — the push does not list the package in the searchable index. Indexing + is a GitHub issue on the index repo (`yoshuawuyts/wasm.directory`), *not* a + config file you push. Two ways to file it, same endpoint: + + - **Tool path** (`component-cli`): from a project with a `[package]` section + in a `wasm.toml`, run `component registry publish` — it reads + `name`/`kind`/`registry`, checks whether the package is already indexed, + and opens the **Registry entry** issue prefilled (`--no-open` prints the + URL instead). + - **By hand**: open the repo's **`registry-entry`** issue template with: + + - **kind**: `component` + - **namespace**: `pulseengine` + - **package name**: `falcon-flight` + - **repository**: `falcon-flight` + - **OCI registry** (new namespaces only): `ghcr.io/pulseengine` Submitting it auto-opens a PR adding `registry/pulseengine.toml`: @@ -64,6 +74,11 @@ cosign verify ghcr.io/pulseengine/falcon-flight:1.127.0 \ already exist and be **public** (step 1) before submitting — an unpullable entry is rejected. Do this only after a real release has populated the package. + > Status: filed for `pulseengine` off falcon-v1.127.0 — + > [wasm.directory#466](https://github.com/yoshuawuyts/wasm.directory/issues/466) + > → auto-opened [PR #467](https://github.com/yoshuawuyts/wasm.directory/pull/467) + > (`registry/pulseengine.toml`), awaiting new-namespace maintainer review. + wasm.directory is **alpha** ("indexed data may be incomplete or reset without notice; don't depend on it in production") — treat the listing as a visibility channel, not a dependency. The durable, signed artifacts remain the GitHub