leaves12138 commented on code in PR #605:
URL: https://github.com/apache/paimon-rust/pull/605#discussion_r3638832665
##########
.github/workflows/release-go-binding.yml:
##########
@@ -144,10 +144,15 @@ jobs:
key: ${{ runner.os }}-${{ runner.arch }}-cargo-${{
hashFiles('**/Cargo.lock') }}
- name: Install cargo-about
+ if: matrix.runner != 'macos-15-intel'
uses: taiki-e/install-action@a6b2e2dcd845ddd7f509ce4f3ed3d922b80cc5d9
# v2.84.0
with:
tool: [email protected]
+ - name: Install cargo-about on Intel macOS
+ if: matrix.runner == 'macos-15-intel'
+ run: cargo install cargo-about --version 0.9.1 --locked --features cli
Review Comment:
[P2] Avoid reinstalling over a cached, untracked binary
This job caches `~/.cargo/bin/` above, but it does not cache Cargo's
`.crates.toml` / `.crates2.json` installation metadata. After a successful
Intel macOS job saves `cargo-about` into that cache, a later run with the same
cache key restores the executable as an untracked binary. This unconditional
`cargo install` then exits with `binary `cargo-about` already exists in
destination` (I reproduced the behavior with a fresh `CARGO_HOME` containing
only the cached binary). Please either version-check and skip when `cargo
about` is already available, or use `--force` when installing. The Python
workflow is not affected because it does not cache `~/.cargo/bin/`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
