chore: bump the emnapi group across 1 directory with 4 updates - #133
chore: bump the emnapi group across 1 directory with 4 updates#133dependabot[bot] wants to merge 2 commits into
Conversation
Bumps the emnapi group with 4 updates in the / directory: [@emnapi/core](https://github.com/toyobayashi/emnapi), [@emnapi/runtime](https://github.com/toyobayashi/emnapi), [@napi-rs/wasm-runtime](https://github.com/napi-rs/napi-rs/tree/HEAD/wasm-runtime) and [emnapi](https://github.com/toyobayashi/emnapi). Updates `@emnapi/core` from 2.0.0-alpha.3 to 2.0.0-alpha.4 - [Release notes](https://github.com/toyobayashi/emnapi/releases) - [Commits](toyobayashi/emnapi@v2.0.0-alpha.3...v2.0.0-alpha.4) Updates `@emnapi/runtime` from 2.0.0-alpha.3 to 2.0.0-alpha.4 - [Release notes](https://github.com/toyobayashi/emnapi/releases) - [Commits](toyobayashi/emnapi@v2.0.0-alpha.3...v2.0.0-alpha.4) Updates `@napi-rs/wasm-runtime` from 1.2.2 to 1.2.3 - [Release notes](https://github.com/napi-rs/napi-rs/releases) - [Changelog](https://github.com/napi-rs/napi-rs/blob/main/wasm-runtime/CHANGELOG.md) - [Commits](https://github.com/napi-rs/napi-rs/commits/@napi-rs/wasm-runtime@1.2.3/wasm-runtime) Updates `emnapi` from 2.0.0-alpha.3 to 2.0.0-alpha.4 - [Release notes](https://github.com/toyobayashi/emnapi/releases) - [Commits](toyobayashi/emnapi@v2.0.0-alpha.3...v2.0.0-alpha.4) --- updated-dependencies: - dependency-name: "@emnapi/core" dependency-version: 2.0.0-alpha.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: emnapi - dependency-name: "@emnapi/runtime" dependency-version: 2.0.0-alpha.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: emnapi - dependency-name: "@napi-rs/wasm-runtime" dependency-version: 1.2.3 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: emnapi - dependency-name: emnapi dependency-version: 2.0.0-alpha.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: emnapi ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 32a62df6e4
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@emnapi/core": "2.0.0-alpha.4", | ||
| "@emnapi/runtime": "2.0.0-alpha.4", | ||
| "@napi-rs/cli": "3.8.2", | ||
| "@napi-rs/wasm-runtime": "1.2.2", | ||
| "@napi-rs/wasm-runtime": "1.2.3", |
There was a problem hiding this comment.
When either WASM package is published, wasm/package.json and npm/wasm32-wasi/package.json still pin @emnapi/core and @emnapi/runtime to 2.0.0-alpha.3 and @napi-rs/wasm-runtime to 1.2.2. Builds and tests therefore exercise the newly selected versions while consumers continue installing the old stack, so the intended runtime fixes never reach the published WASM paths and the tested dependency combination differs from the released one. Update both published manifests alongside these root pins.
AGENTS.md reference: AGENTS.md:L158-L160
Useful? React with 👍 / 👎.
Bumps the emnapi group with 4 updates in the / directory: @emnapi/core, @emnapi/runtime, @napi-rs/wasm-runtime and emnapi.
Updates
@emnapi/corefrom 2.0.0-alpha.3 to 2.0.0-alpha.4Release notes
Sourced from @emnapi/core's releases.
Commits
9e66b632.0.0-alpha.4e081d0cfix: finalizer queue O(n) cleanup (#234)53c3b81fix flaky test8d1b4dfperf: optimize runtime and hot paths (#232)c7cf324test: browser test (#231)7d68409test: parallel test (#229)7a5bf16test: experiment vitest (#228)Updates
@emnapi/runtimefrom 2.0.0-alpha.3 to 2.0.0-alpha.4Release notes
Sourced from @emnapi/runtime's releases.
Commits
9e66b632.0.0-alpha.4e081d0cfix: finalizer queue O(n) cleanup (#234)53c3b81fix flaky test8d1b4dfperf: optimize runtime and hot paths (#232)c7cf324test: browser test (#231)7d68409test: parallel test (#229)7a5bf16test: experiment vitest (#228)Updates
@napi-rs/wasm-runtimefrom 1.2.2 to 1.2.3Changelog
Sourced from @napi-rs/wasm-runtime's changelog.
Commits
70c1493chore(release): publishaeba312fix(cli): compatible with emnapi v1 & v2 (#3454)b8ba732fix(deps): update emnapi to v2.0.0-alpha.4 (#3451)9c10fc5build(wasm-runtime): use Rolldown (#3429)Updates
emnapifrom 2.0.0-alpha.3 to 2.0.0-alpha.4Release notes
Sourced from emnapi's releases.
Commits
9e66b632.0.0-alpha.4e081d0cfix: finalizer queue O(n) cleanup (#234)53c3b81fix flaky test8d1b4dfperf: optimize runtime and hot paths (#232)c7cf324test: browser test (#231)7d68409test: parallel test (#229)7a5bf16test: experiment vitest (#228)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions