You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TLDR; is that it is to improve the repeatability and documentation of the tools/environments used to build the WASM blobs that end up in Node.js
I believe I have agreement from the maintainers of the deps in Node.js that include WASM (undici, amaro, cjs-module-lexer)
The existing repo has the config and actions needed to build the container and publish releases. It will need to be updated to use a token which is needed by the release please automation. PR to request new token - #926
The text was updated successfully, but these errors were encountered:
This issue is to get agreement to move the repo https://github.com/mhdawson/wasm-builder to the organization.
The repo will be used to manage the container used to build WASM blobs within the dependencies of Node.js.
You can read more about the what/why in - nodejs/security-wg#1236 (comment)
The TLDR; is that it is to improve the repeatability and documentation of the tools/environments used to build the WASM blobs that end up in Node.js
I believe I have agreement from the maintainers of the deps in Node.js that include WASM (undici, amaro, cjs-module-lexer)
The existing repo has the config and actions needed to build the container and publish releases. It will need to be updated to use a token which is needed by the release please automation. PR to request new token - #926
The text was updated successfully, but these errors were encountered: