Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation on packaging and publishing WIT packages #690

Open
brooksmtownsend opened this issue Nov 7, 2024 · 1 comment
Open

Documentation on packaging and publishing WIT packages #690

brooksmtownsend opened this issue Nov 7, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed stale

Comments

@brooksmtownsend
Copy link
Member

In our documentation we have information about how to build and publish Wasm components, and with the introduction of wkg I think we should add information about how to build and publish WIT packages (as Wasm).

Additionally, I think we can offer some guidance here as well, e.g. if you're publishing a component other folks are going to compose with over the interface wasmcloud:blobby/foobar, the interface goes to ghcr.io/wasmcloud/wasmcloud/blobby:0.2.0 and the component goes to ghcr.io/wasmcloud/blobby:0.2.0?

cc @thomastaylor312

@brooksmtownsend brooksmtownsend added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Nov 7, 2024
Copy link

stale bot commented Jan 6, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!

@stale stale bot added the stale label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed stale
Projects
None yet
Development

No branches or pull requests

1 participant