targeting correct workflow reference prior to merging
What the developer wrote
Authored by Mathias BROUSSET
targeting correct workflow reference prior to merging
What changed, and why it matters
This commit simply changes a GitHub Actions workflow to point at the correct, stable version of a reusable deployment workflow. It is a normal repository hygiene fix with no security relevance visible in the diff.
No security action required; treat as routine CI/CD maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The deploy_packages.yml workflow was referencing a branch-named reusable workflow (mbr/reusable-workflow-jfrog-npm) and is now pinned to the v1 tag of the correctly named reusable workflow (reusable_npm_deployment.yml). This is a one-line reference correction; no code, permissions, secrets, or deployment logic changed.
Changed components
.github/workflows/deploy_packages.ymlInspect captured patch +1 / −1
diff --git a/.github/workflows/deploy_packages.yml b/.github/workflows/deploy_packages.yml
index aae321d..68a5287 100644
--- a/.github/workflows/deploy_packages.yml
+++ b/.github/workflows/deploy_packages.yml
@@ -9,6 +9,6 @@ on:
jobs:
deploy_js_client:
name: Deploy js client to jfrog and npmjs.com
- uses: LedgerHQ/ledger-app-workflows/.github/workflows/reusable_deployment_npm.yml@mbr/reusable-workflow-jfrog-npm
+ uses: LedgerHQ/ledger-app-workflows/.github/workflows/reusable_npm_deployment.yml@v1
with:
package_directory: "bitcoin_client_js"
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.