docs(oci): make the wasm.directory registration step concrete - #305
Merged
Conversation
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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG
7 tasks
avrabe
enabled auto-merge (squash)
July 22, 2026 21:10
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 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The
docs/OCI-DISTRIBUTION.mdregistration step (step 2, "register the namespace with wasm.directory") was vague — it said to "add the namespace → ghcr.io mapping to the wasm.directory registry config", which doesn't match how wasm.directory actually works.The actual mechanism
Registration is a GitHub issue on the index repo (
yoshuawuyts/wasm), not a config file you push:registry-entryissue template with kind=component, namespace=pulseengine, package=falcon-flight, repository=falcon-flightregistry/pulseengine.toml:Why now
I'm validating the ghcr OCI push end-to-end (release re-run for v1.127.0). This documents the exact registration fields the org owner will need for step 2, so the mechanism doesn't have to be re-derived when the package goes public.
Docs-only; no crates/artifacts/CI touched.
🤖 Generated with Claude Code