do NOT do a github release upon new pypi deployment
What the developer wrote
Authored by Mathias BROUSSET
do NOT do a github release upon new pypi deployment
What changed, and why it matters
This commit changes a single setting in the project's automated CI workflow. It stops GitHub from automatically creating a new GitHub Release every time a new Python package is published to PyPI. This is a workflow/process change, not a code change affecting the app, wallet, or any security-sensitive functionality.
No security action required. Treat as a normal repository maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In .github/workflows/ci-workflow.yml, the release input to a reusable deployment workflow is changed from true to false. The publish input remains true, so PyPI deployments continue, but no corresponding GitHub Release will be generated. There is no modification to application code, cryptography, transaction parsing, or device communication.
Changed components
.github/workflows/ci-workflow.ymlInspect captured patch +1 / −1
diff --git a/.github/workflows/ci-workflow.yml b/.github/workflows/ci-workflow.yml
index c6add67..fe33c5a 100644
--- a/.github/workflows/ci-workflow.yml
+++ b/.github/workflows/ci-workflow.yml
@@ -249,7 +249,7 @@ jobs:
package_name: ledger_bitcoin
package_directory: ./bitcoin_client/
jfrog_deployment: true
- release: true
+ release: false
publish: true
secrets:
pypi_token: ${{ secrets.PYPI_PUBLIC_API_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.