cargo-near
Advanced tools
Comparing version 0.13.2 to 0.13.3
@@ -10,2 +10,10 @@ # Changelog | ||
## [0.13.3](https://github.com/near/cargo-near/compare/cargo-near-v0.13.2...cargo-near-v0.13.3) - 2025-01-22 | ||
### Other | ||
- update near-cli-rs to 0.18.0 (#293) | ||
- update `cargo near new` template `image` and `image_digest` ([#288](https://github.com/near/cargo-near/pull/288)) | ||
- update `cargo near new` template `image` and `image_digest` ([#283](https://github.com/near/cargo-near/pull/283)) | ||
## [0.13.2](https://github.com/near/cargo-near/compare/cargo-near-v0.13.1...cargo-near-v0.13.2) - 2024-12-19 | ||
@@ -12,0 +20,0 @@ |
@@ -26,3 +26,3 @@ { | ||
"name": "cargo-near", | ||
"version": "0.13.2" | ||
"version": "0.13.3" | ||
}, | ||
@@ -715,3 +715,3 @@ "node_modules/@isaacs/cliui": { | ||
"requires": true, | ||
"version": "0.13.2" | ||
"version": "0.13.3" | ||
} |
{ | ||
"artifactDownloadUrl": "https://github.com/near/cargo-near/releases/download/cargo-near-v0.13.2", | ||
"artifactDownloadUrl": "https://github.com/near/cargo-near/releases/download/cargo-near-v0.13.3", | ||
"author": "Near Inc <hello@nearprotocol.com>", | ||
@@ -97,3 +97,3 @@ "bin": { | ||
}, | ||
"version": "0.13.2", | ||
"version": "0.13.3", | ||
"volta": { | ||
@@ -100,0 +100,0 @@ "node": "18.14.1", |
@@ -196,3 +196,41 @@ <!-- markdownlint-disable MD014 --> | ||
## Special `cargo` environment variables | ||
Both of the following are mentioned on https://doc.rust-lang.org/cargo/reference/config.html#buildrustflags | ||
### `RUSTFLAGS` | ||
running e.g. | ||
```bash | ||
RUSTFLAGS="your_custom_value" cargo near build non-reproducible-wasm | ||
``` | ||
won't result in `"your_custom_value"` affecting the build. | ||
`RUSTFLAGS="-Awarnings"` is always used for abi build stage, and `RUSTFLAGS="-C link-arg=-s"` for wasm build stage. | ||
Logic for concatenating default values of this variable with values from env was removed in `cargo-near-0.13.3`/`cargo-near-build-0.4.3`, as it was seen as | ||
an unnecessary complication. | ||
There's still a way to override this parameter for wasm build stage, e.g.: | ||
```lang | ||
cargo near build non-reproducible-wasm --env 'RUSTFLAGS=--verbose' | ||
RUST_LOG=info cargo near build non-reproducible-wasm --env 'RUSTFLAGS=--verbose -C link-arg=-s' | ||
``` | ||
### `CARGO_ENCODED_RUSTFLAGS` | ||
This variable is always unset during build, so | ||
```bash | ||
CARGO_ENCODED_RUSTFLAGS="your_custom_value" cargo near build non-reproducible-wasm | ||
``` | ||
won't result in `"your_custom_value"` affecting the build. | ||
This is so to avoid weird issues like [#287](https://github.com/near/cargo-near/issues/287) when composing multiple builds via build scripts. | ||
## Contribution | ||
@@ -199,0 +237,0 @@ |
72069
251