⚙️ (jfrog) [NO-ISSUE]: Push lib to jfrog artifactory

[dedsxc]

📝 Description

Replace this text by a clear and concise description of what this pull request is about and why it is needed. Be sure to explain the problem you're addressing and the solution you're proposing.
For libraries, you can add a code sample of how to use it.
For bugfixes, you can explain the previous behavior and how it was fixed.
In case of visual features, please attach screenshots or video recordings to demonstrate the changes.

❓ Context

• JIRA or GitHub link:

✅ Checklist

Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

• Covered by automatic tests.
• Impact of the changes:
  • ...

---

🧐 Checklist for the PR Reviewers

• The code aligns with the requirements described in the linked JIRA or GitHub issue.
• The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
• There are no undocumented trade-offs, technical debt, or maintainability issues.
• The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
• Any new dependencies have been justified and documented.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
device-sdk-ts-sample	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 5, 2024 1:21pm

[github-actions]

Fails

🚫

Please fix the PR branch name to match the convention, see this documentation. Wrong branch name: INFRAPRJ-6604 ℹ️ Regex to match: /^(feature|feat|bugfix|bug|hotfix|fix|support|chore|core|doc|refacto|refactor)\/((dsdk)-[0-9]+|no-issue)-.+/i Rules: Must start with a type (feature, bugfix, hotfix, support, chore, core, doc, refacto) Followed by a SLASH ("/") Followed by a JIRA issue number (DSDK-1234) or "no-issue" Followed by a DASH ("-") Followed by a description ℹ️ Example: feat/dsdk-1234-my-feature

Generated by 🚫 dangerJS against 9b7d8b5

[vercel]

@AEnguerrand is attempting to deploy a commit to the LedgerHQ Team on Vercel.

To accomplish this, @AEnguerrand needs to request access to the Team.

Afterwards, an owner of the Team is required to accept their membership request.

If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account.

[valpinkman]

[ASK] can you reset the environment needed to production (we have special rules that require an approval from one of the team members to go through with production workflows)

[valpinkman]

[SHOULD] please don't remove the private: true from the root package.json