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

Figure out new Github release pipeline #167

Open
SebastienGllmt opened this issue Jan 22, 2023 · 0 comments
Open

Figure out new Github release pipeline #167

SebastienGllmt opened this issue Jan 22, 2023 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@SebastienGllmt
Copy link
Contributor

SebastienGllmt commented Jan 22, 2023

Right now we have a single Github release per CML version, but this won't work as-is anymore because we've transitioned this to be a multi-repo.

As an additional note, one of the largest consumers of CML is Lucid by @alessandrokonrad which he consumed through Deno. Deno requires a special wasm-pack build command and Deno's suggestion is to publish deno package by hosting them on tags for your repo (https://deno.land/add_module).

I should note this Deno is case is not too dissimilar to the wasm-pack build --target=web case which also can't be published to npm and so is in a similar boat

Not sure what the best way to satisfy all these requirements are.

@SebastienGllmt SebastienGllmt added the help wanted Extra attention is needed label Jan 22, 2023
@gostkin gostkin moved this to Unscheduled in Tooling team development board Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
Development

No branches or pull requests

1 participant