What the developer wrote
Authored by Mathias BROUSSET
update crate deployment
What changed, and why it matters
This commit removes two lines from a GitHub Actions CI workflow file. It disables a JFrog deployment step and stops passing a Cargo crate publishing token to that workflow job. There is no change to the actual Bitcoin app code, cryptography, or anything users install on their Ledger devices. It is purely an internal adjustment to how a Rust client library crate is published.
No security action required. Treat as a routine CI/CD maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies .github/workflows/ci-workflow.yml, deleting jfrog_deployment: true and the secrets.cargo_token input for a reusable workflow job that publishes the bitcoin_client_rs crate. No application source code, build logic, transaction parsing, or cryptographic code is touched. The change appears to switch crate publishing from a JFrog-based deployment path back to a standard crates.io release path (publish: true is retained).
Changed components
.github/workflows/ci-workflow.ymlInspect captured patch +0 / −3
diff --git a/.github/workflows/ci-workflow.yml b/.github/workflows/ci-workflow.yml
index e0a3366..062b50f 100644
--- a/.github/workflows/ci-workflow.yml
+++ b/.github/workflows/ci-workflow.yml
@@ -303,6 +303,3 @@ jobs:
package_directory: "bitcoin_client_rs"
publish: true
release: false
- jfrog_deployment: true
- secrets:
- cargo_token: ${{ secrets.CARGO_CRATES_TOKEN }}
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.