Yarn Upgrade

[bh2smith]

User description

Also includes higher version bumps of near-ca and near-api-js

---

PR Type

dependencies

---

Description

• Upgraded near-api-js dependency from version 4.0.3 to 5.0.0.
• Upgraded near-ca dependency from version 0.4.1 to 0.5.2.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Upgrade `near-api-js` and `near-ca` dependencies                  package.json Upgraded near-api-js from version 4.0.3 to 5.0.0 Upgraded near-ca from version 0.4.1 to 0.5.2 +2/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[mintbase-codium-pr-agent]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[mintbase-codium-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Pin the version of "near-api-js" to avoid potential breaking changes Consider pinning the version of "near-api-js" to "5.0.0" instead of using "^5.0.0" to ensure consistent behavior across different environments and avoid potential breaking changes in minor version updates. package.json [46] -"near-api-js": "^5.0.0", +"near-api-js": "5.0.0", Suggestion importance[1-10]: 8 Why: Pinning the version of "near-api-js" to "5.0.0" instead of using "^5.0.0" is a best practice to ensure consistent behavior and avoid potential breaking changes in minor version updates.	8
	Pin the version of "near-ca" to avoid potential breaking changes Consider pinning the version of "near-ca" to "0.5.2" instead of using "^0.5.2" to ensure consistent behavior across different environments and avoid potential breaking changes in minor version updates. package.json [47] -"near-ca": "^0.5.2" +"near-ca": "0.5.2", Suggestion importance[1-10]: 8 Why: Pinning the version of "near-ca" to "0.5.2" instead of using "^0.5.2" is a best practice to ensure consistent behavior and avoid potential breaking changes in minor version updates.	8