Stream: wasi

Topic: Github packages


view this post on Zulip Lann Martin (Sep 18 2025 at 16:33):

It could be that there are permissions issues in the webassembly org but here I was able to associate a package with a repo with a completely different name.

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

view this post on Zulip Lann Martin (Sep 18 2025 at 16:33):

@Bailey Hayes @Yosh Wuyts

view this post on Zulip Bailey Hayes (Sep 18 2025 at 16:35):

It's more for the downstream consumers. They point to wasi:http and wkg defaults to WebAssembly/wasi

view this post on Zulip Lann Martin (Sep 18 2025 at 16:37):

Can the existing Github packages be changed to point at their respective repos without renaming them?

view this post on Zulip Bailey Hayes (Sep 18 2025 at 16:39):

We use oci labels to associate repos. We want a different URI path so that we aren't publishing to org level

view this post on Zulip Lann Martin (Sep 18 2025 at 16:49):

Ah I see what you're saying, but that isn't quite how wkg is constructing the OCI reference. The wasi.dev registry just resolves to the prefix ghcr.io/webassembly/ (here); the wasi/ part is derived from the wasi:* package namespace. I couldn't use : because it is reserved in OCI so I went with / :shrug:

view this post on Zulip Lann Martin (Sep 18 2025 at 16:50):

AFAIK in Github Packages everything after ghcr.io/<org>/ is opaque; the wasi/ there isn't meaningful to GH or OCI.

view this post on Zulip Lann Martin (Sep 18 2025 at 16:55):

For this example package I can do wkg get fermyon:wasi-http-dump --registry fermyon.com; the registry fermyon.com leads to a lookup of https://www.fermyon.com/.well-known/wasm-pkg/registry.json which is used to construct the OCI reference ghcr.io/fermyon/wasm-pkg/fermyon/wasi-http-dump which is completely different from the linked repository https://github.com/fermyon/wasi-hyperium

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.
Contribute to fermyon/wasi-hyperium development by creating an account on GitHub.

view this post on Zulip Bailey Hayes (Sep 18 2025 at 17:02):

with well known, is it possible to configure more than just the prefix like a map? We could hardcode the paths to each wasi package. For example if the namespace prefix was just "WebAssembly" and path to artifact "wasi-http/wit"

view this post on Zulip Lann Martin (Sep 18 2025 at 17:03):

Not currently

view this post on Zulip Lann Martin (Sep 18 2025 at 17:04):

The <namespace>/<name>:<version> suffix is fixed

view this post on Zulip Lann Martin (Sep 18 2025 at 17:05):

Could you say more about wanting to customize the OCI namespace?


Last updated: Dec 06 2025 at 06:05 UTC