From 2caeaecc5673fbfd55de460b07cd5389d915143c Mon Sep 17 00:00:00 2001 From: Darioush Jalali Date: Tue, 17 Mar 2026 05:35:41 -0700 Subject: [PATCH 1/3] doc(docs): remove outdated cargo build notes Co-Authored-By: Claude Opus 4.6 (1M context) --- docs/archival/run-archival-node.md | 12 ------------ docs/rpc/run-rpc-node.md | 10 ---------- docs/validator/compile-and-run-a-node.md | 18 ------------------ 3 files changed, 40 deletions(-) diff --git a/docs/archival/run-archival-node.md b/docs/archival/run-archival-node.md index fe1a379..3c2ce8e 100644 --- a/docs/archival/run-archival-node.md +++ b/docs/archival/run-archival-node.md @@ -84,12 +84,6 @@ takes approximately 25 minutes). Note that compilation will need over with processes being killed, you might want to try reducing number of parallel jobs, for example: `CARGO_BUILD_JOBS=8 make release`. -By the way, if you’re familiar with Cargo, you could wonder why not -run `cargo build -p neard --release` instead. While this will produce -a binary, the result will be a less optimized version. On technical -level, this is because building via `make neard` enables link-time -optimisation which is disabled by default. - The binary path is `target/release/neard` ### 3. Initialize working directory {#3-initialize-working-directory} @@ -178,12 +172,6 @@ takes approximately 25 minutes). Note that compilation will need over with processes being killed, you might want to try reducing number of parallel jobs, for example: `CARGO_BUILD_JOBS=8 make release`. -By the way, if you’re familiar with Cargo, you could wonder why not -run `cargo build -p neard --release` instead. While this will produce -a binary, the result will be a less optimized version. On technical -level, this is because building via `make neard` enables link-time -optimisation which is disabled by default. - The binary path is `target/release/neard` ### 3. Initialize working directory {#3-initialize-working-directory-1} diff --git a/docs/rpc/run-rpc-node.md b/docs/rpc/run-rpc-node.md index eb34f5f..18092e5 100644 --- a/docs/rpc/run-rpc-node.md +++ b/docs/rpc/run-rpc-node.md @@ -83,11 +83,6 @@ takes approximately 25 minutes). Note that compilation will need over with processes being killed, you might want to try reducing number of parallel jobs, for example: `CARGO_BUILD_JOBS=8 make release`. -If you’re familiar with Cargo, you could also run `cargo build -p neard ---release` instead, which might or might not be equivalent to `make release`. It -is equivalent at the time of writing, but we don't guarantee this. If in doubt, -consult the `Makefile`, or just stick with `make release`. - The binary path is `target/release/neard` ### 3. Initialize working directory {#3-initialize-working-directory} @@ -171,11 +166,6 @@ takes approximately 25 minutes). Note that compilation will need over with processes being killed, you might want to try reducing number of parallel jobs, for example: `CARGO_BUILD_JOBS=8 make release`. -If you’re familiar with Cargo, you could also run `cargo build -p neard ---release` instead, which might or might not be equivalent to `make release`. It -is equivalent at the time of writing, but we don't guarantee this. If in doubt, -consult the `Makefile`, or just stick with `make release`. - The binary path is `target/release/neard` ### 3. Initialize working directory {#3-initialize-working-directory-1} diff --git a/docs/validator/compile-and-run-a-node.md b/docs/validator/compile-and-run-a-node.md index c723cfd..0d15ec9 100644 --- a/docs/validator/compile-and-run-a-node.md +++ b/docs/validator/compile-and-run-a-node.md @@ -106,12 +106,6 @@ takes approximately 25 minutes). Note that compilation will need over with processes being killed, you might want to try reducing number of parallel jobs, for example: `CARGO_BUILD_JOBS=8 make neard`. -By the way, if you’re familiar with Cargo, you could wonder why not -run `cargo build -p neard --release` instead. While this will produce -a binary, the result will be a less optimized version. On technical -level, this is because building via `make neard` enables link-time -optimisation which is disabled by default. The binary path is `target/release/neard`. - For `localnet`, you also have the option to build in nightly mode (which is experimental and is used for cutting-edge testing). When you compile, use the following command: ```bash @@ -180,12 +174,6 @@ takes approximately 25 minutes). Note that compilation will need over with processes being killed, you might want to try reducing number of parallel jobs, for example: `CARGO_BUILD_JOBS=8 make neard`. -By the way, if you’re familiar with Cargo, you could wonder why not -run `cargo build -p neard --release` instead. While this will produce -a binary, the result will be a less optimized version. On technical -level, this is because building via `make neard` enables link-time -optimisation which is disabled by default. - The binary path is `target/release/neard` ### 3. Initialize working directory {#initialize-working-directory-1} @@ -415,12 +403,6 @@ takes approximately 25 minutes). Note that compilation will need over with processes being killed, you might want to try reducing number of parallel jobs, for example: `CARGO_BUILD_JOBS=8 make neard`. -By the way, if you’re familiar with Cargo, you could wonder why not -run `cargo build -p neard --release` instead. While this will produce -a binary, the result will be a less optimized version. On technical -level, this is because building via `make neard` enables link-time -optimisation which is disabled by default. - The binary path is `target/release/neard` ### 3. Initialize working directory {#initialize-working-directory-2} From 172ad9c6d8b6f91aa53325b276a8dc1d1c286e5d Mon Sep 17 00:00:00 2001 From: Darioush Jalali Date: Tue, 17 Mar 2026 06:30:03 -0700 Subject: [PATCH 2/3] doc(docs): restore binary path note in localnet section Co-Authored-By: Claude Opus 4.6 (1M context) --- docs/validator/compile-and-run-a-node.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/validator/compile-and-run-a-node.md b/docs/validator/compile-and-run-a-node.md index 0d15ec9..850f32d 100644 --- a/docs/validator/compile-and-run-a-node.md +++ b/docs/validator/compile-and-run-a-node.md @@ -106,6 +106,7 @@ takes approximately 25 minutes). Note that compilation will need over with processes being killed, you might want to try reducing number of parallel jobs, for example: `CARGO_BUILD_JOBS=8 make neard`. +The binary path is `target/release/neard`. For `localnet`, you also have the option to build in nightly mode (which is experimental and is used for cutting-edge testing). When you compile, use the following command: ```bash From 8c55afe9471b89c7cc4331ca71d245a09ca622f9 Mon Sep 17 00:00:00 2001 From: Darioush Jalali Date: Tue, 17 Mar 2026 06:49:03 -0700 Subject: [PATCH 3/3] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- docs/validator/compile-and-run-a-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/validator/compile-and-run-a-node.md b/docs/validator/compile-and-run-a-node.md index 850f32d..d8f9008 100644 --- a/docs/validator/compile-and-run-a-node.md +++ b/docs/validator/compile-and-run-a-node.md @@ -106,7 +106,7 @@ takes approximately 25 minutes). Note that compilation will need over with processes being killed, you might want to try reducing number of parallel jobs, for example: `CARGO_BUILD_JOBS=8 make neard`. -The binary path is `target/release/neard`. +The binary path is `target/release/neard` For `localnet`, you also have the option to build in nightly mode (which is experimental and is used for cutting-edge testing). When you compile, use the following command: ```bash