💄 (smpl) [NO-ISSUE]: Fix package json conflict

[jdabbech-ledger]

📝 Description

Package json conflict resolution

❓ Context

• JIRA or GitHub link: [NO-ISSUE]

• Feature:

✅ Checklist

Pull Requests must pass CI checks and undergo code review. Set the PR as Draft if it is not yet ready for review.

• Covered by automatic tests
• Changeset is provided
• Impact of the changes:
  • list 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	Dec 17, 2024 1:02pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
doc-device-management-kit	⬜️ Ignored (Inspect)			Dec 17, 2024 1:02pm

[github-actions]

Fails

🚫

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

	Messages
⚠️	No changeset file found in the PR. Please add a changeset file.

Generated by 🚫 dangerJS against 5311b00