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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo install wasm-pack --version 0.12.1
fails on MacOS
#1365
Comments
Also seeing this in our GitHub Actions CI - so not sure this is MacOS specific. |
Looks like an upstream issue with the hoot crate - algesten/hoot#1 |
camscale
added a commit
to gravitational/teleport
that referenced
this issue
Jan 30, 2024
When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365
camscale
added a commit
to gravitational/teleport
that referenced
this issue
Jan 30, 2024
When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365
camscale
added a commit
to gravitational/teleport
that referenced
this issue
Jan 30, 2024
When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365
github-merge-queue bot
pushed a commit
to gravitational/teleport
that referenced
this issue
Jan 30, 2024
* build: Ensure pinned versions when installing wasm-pack When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365 * Update e ref for version pinned cargo build of wasm-pack
github-merge-queue bot
pushed a commit
to gravitational/teleport
that referenced
this issue
Jan 30, 2024
* [v15] build: Ensure pinned versions when installing wasm-pack When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365 * Update e ref for version pinned cargo build of wasm-pack
Confirmed that |
@ibeckermayer Are you building locally with docker/finch? If so your local build works probably because of the cache, try again with |
github-merge-queue bot
pushed a commit
to gravitational/teleport
that referenced
this issue
Jan 30, 2024
* [v15] build: Ensure pinned versions when installing wasm-pack When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365 * Update e ref for version pinned cargo build of wasm-pack
github-merge-queue bot
pushed a commit
to gravitational/teleport
that referenced
this issue
Jan 30, 2024
* build: Ensure pinned versions when installing wasm-pack When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365 * Update e ref for version pinned cargo build of wasm-pack
github-merge-queue bot
pushed a commit
to gravitational/teleport
that referenced
this issue
Jan 31, 2024
* [v15] build: Ensure pinned versions when installing wasm-pack When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365 * Update e ref for version pinned cargo build of wasm-pack
camscale
added a commit
to gravitational/teleport
that referenced
this issue
Jan 31, 2024
When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365
github-merge-queue bot
pushed a commit
to gravitational/teleport
that referenced
this issue
Jan 31, 2024
* build: Ensure pinned versions when installing wasm-pack When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365 * Update e ref for version pinned cargo build of wasm-pack
camscale
added a commit
to gravitational/teleport
that referenced
this issue
Jan 31, 2024
When installing `wasm-pack` with `cargo`, use the `--locked` flag to ensure the versions referenced in the Cargo.lock file are used and not any newer versions. This creates a repeatable build and insulates us from upstream breakage in new versions. In particular an upstream version change included the hoot-0.1.2 dependency on a new build which fails to build with rust 1.71.1, which is the version we are using. Link: rustwasm/wasm-pack#1365
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃悰 Bug description
cargo install wasm-pack --version 0.12.1
is failing on MacOS with the following error log:This was apparently working for us previously (both locally, and in CI) but has stopped.
馃 Expected Behavior
It should build successfully
馃憻 Steps to reproduce
Set up the environment and run
cargo install wasm-pack --version 0.12.1
馃實 Your environment
Include the relevant details of your environment.
wasm-pack version:
wasm-pack 0.12.1
rustc version:
rustc 1.71.1 (eb26296b5 2023-08-03)
macOS:
macOS Sonoma 14.3 (23D56)
on M1 chip (locally)The text was updated successfully, but these errors were encountered: