Stream: jco

Topic: ✔ jco v1.11.0 release


view this post on Zulip Victor Adossi (Apr 28 2025 at 20:05):

Hey all, jco v1.11.0 has been released:

https://www.npmjs.com/package/@bytecodealliance/jco/v/1.11.0
https://github.com/bytecodealliance/jco/releases/tag/jco-v1.11.0

There's been a few changes to jco since the last release and not everything can/should be in the changelog so some quick notes:

Going forward, js-component-bindgen, jco, and p2-shim will have similar release notes generated (but only contain commits w/ the right conventional commit scope), and hopefully I can even automate posting this message as well here.

There's still quite a bit to do (ex. the release notes look bare for any given project right now), but please feel free to pull the new release and kick the tires.

For the full list of commits (this contains various packages):

https://github.com/bytecodealliance/jco/compare/1.10.2...jco-v1.11.0

JavaScript tooling for working with WebAssembly Components. Latest version: 1.11.0, last published: 3 minutes ago. Start using @bytecodealliance/jco in your project by running `npm i @bytecodealliance/jco`. There are 9 other projects in the npm registry using @bytecodealliance/jco.
Changelog All notable changes to this project will be documented in this file. [jco-v1.11.0] - 2025-04-28 🚀 Features (jco) expose comoponentizejs's debugBuild option on command line (#633) by @pch...
JavaScript toolchain for working with WebAssembly Components - Comparing 1.10.2...jco-v1.11.0 · bytecodealliance/jco

view this post on Zulip Notification Bot (Apr 28 2025 at 20:09):

Victor Adossi has marked this topic as resolved.

view this post on Zulip Lann Martin (Apr 28 2025 at 20:44):

We're seeing our builds breaking with this release: https://github.com/bytecodealliance/jco/issues/646

Was this intentional? It is causing downstream build failures like spinframework/spin-js-sdk#362.

view this post on Zulip Victor Adossi (Apr 29 2025 at 03:50):

Thanks for the report -- commented in the issue, just did the 1.11.1 release now after the deprecation of 1.11.0. The package has dependents so it can't be unpublished (getting in touch with npm support for that)

view this post on Zulip Victor Adossi (Apr 29 2025 at 03:53):

Please try 1.11.1! I've done a manual release, and the fix for the packaging situation will be merged soon

This commit fixes the automated release issue caused by obj/* files not being included in the packaged tarball. This step should have been pre pack rather than prepublish.

Last updated: Dec 06 2025 at 06:05 UTC