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

Adopt v4.2.8 #7

Open
wants to merge 710 commits into
base: stylus
Choose a base branch
from
Open

Adopt v4.2.8 #7

wants to merge 710 commits into from

Conversation

rachel-bousfield
Copy link
Contributor

Adopts wasmer v4.2.8

maminrayej and others added 30 commits February 1, 2024 02:40
Try to build the package before publishing it
Generally when userspace tries to do something the environment can't do (even if it might be able to do it in the future), the usual response is the return a "Not Supported" error, rather than crashing the entire environment.
The new version was using hyper 1.0.
We need to wait with that until we can upgrade the whole stack,
including reqwest.
Avoids a duplicate dependency
…eqGen

[SINGLEPASS]Fix bug #4092 which was due to resource leak while doing …
…binations, zero copy on hashing and an optimized extent resolution
xdoardo and others added 26 commits March 28, 2024 11:55
…ance-on-aarch64-popcnt-select

feat(singlepass): use SIMD insts for popcount
this makes it so app.yaml can process owner field in two ways,

In desdcending order of priority:
- via the `--owner` flag passed to the CLI
- via the `owner` field in the app.yaml
The module was renamed to winterjs.
the owner field was being set to the same namespace as the package. This means
if the package is `wasmer/hello` then the owner becomes `wasmer`.

This PR also adds the owner field to app.yaml generated by `wasmer app create`
The advisory is not relevant for us, it's a denial of service vector for
servers.

The advisory fails the cargo-deny checks though, so the upgrade is
needed.

Details:  https://rustsec.org/advisories/RUSTSEC-2024-0332
deps: Upgrade h2 due to RUSTSEC advisory
Various fixes detected in the build
Copy link
Member

@joshuacolvin0 joshuacolvin0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.