fix: bump non-breaking dependencies to latest

[aversini]

PR Type

enhancement, dependencies

---

Description

• Updated several non-breaking dependencies to their latest versions to ensure compatibility and leverage new features.
• Updated the pnpm package manager to a newer version for improved performance and features.
• Made a minor formatting change in the files array in packages/auth-provider/package.json.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Update development dependencies and package manager version package.json Updated @versini/dev-dependencies-client to version 6.0.1. Updated @versini/dev-dependencies-types to version 1.3.4. Updated pnpm package manager to version 9.8.0. +3/-3      package.json Update dependencies and format files array                              packages/auth-provider/package.json Updated @versini/ui-hooks to version 4.1.0. Updated jose to version 5.7.0. Minor formatting change in the files array. +3/-5
Additional files (token-limit)	pnpm-lock.yaml ...                                                                                                            pnpm-lock.yaml ... +554/-552

---

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

[qodo-merge-pro]

PR Reviewer Guide 🔍

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Use caret version ranges for dependencies to allow automatic minor version updates Consider using a caret (^) version range for the @versini/ui-hooks and jose dependencies to allow for minor version updates automatically. This can help keep the project up-to-date with bug fixes and non-breaking changes. packages/auth-provider/package.json [47-48] -"@versini/ui-hooks": "4.1.0", -"jose": "5.7.0", +"@versini/ui-hooks": "^4.1.0", +"jose": "^5.7.0", Apply this suggestion Suggestion importance[1-10]: 8 Why: Using caret version ranges is a best practice that allows for automatic minor updates, which can help keep the project up-to-date with bug fixes and non-breaking changes. This suggestion is relevant and beneficial for maintaining the dependencies.	8
Enhancement	Update package version specifier to allow for compatible updates Consider updating the @versini/dev-dependencies-client package to the latest version that is compatible with your project's requirements. This may include new features, bug fixes, or performance improvements. pnpm-lock.yaml [15-16] '@versini/dev-dependencies-client': - specifier: 6.0.1 + specifier: ^6.0.1 version: 6.0.1(@microsoft/[email protected](@types/[email protected]))(@swc/[email protected](@swc/[email protected]))(@swc/[email protected])(@types/[email protected])(@types/[email protected])(@types/[email protected])([email protected])([email protected])([email protected])([email protected])([email protected])([email protected]([email protected]))([email protected])([email protected])([email protected])([email protected]) Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion to update the package version specifier to allow for compatible updates is valid and can help ensure that the project benefits from the latest features and fixes. However, it is not critical and should be evaluated against project-specific compatibility requirements.	7
	Use more flexible version ranges for devDependencies to allow minor updates Consider using a more flexible version range for the @versini/dev-dependencies-client and @versini/dev-dependencies-types devDependencies. This can help ensure compatibility with other packages while still allowing for minor updates. package.json [18-19] -"@versini/dev-dependencies-client": "6.0.1", -"@versini/dev-dependencies-types": "1.3.4" +"@versini/dev-dependencies-client": "^6.0.1", +"@versini/dev-dependencies-types": "^1.3.4" Apply this suggestion Suggestion importance[1-10]: 7 Why: This suggestion promotes using flexible version ranges for devDependencies, which can help ensure compatibility with other packages while allowing for minor updates. It is a good practice for maintaining the development environment.	7
Maintainability	Simplify the packageManager field by removing the SHA512 hash Consider removing the sha512 hash from the packageManager field. While it provides integrity, it may make it harder to update the package manager version in the future. Using only the version number is often sufficient. package.json [21] -"packageManager": "[email protected]+sha512.8e4c3550fb500e808dbc30bb0ce4dd1eb614e30b1c55245f211591ec2cdf9c611cabd34e1364b42f564bd54b3945ed0f49d61d1bbf2ec9bd74b866fcdc723276" +"packageManager": "[email protected]" Apply this suggestion Suggestion importance[1-10]: 6 Why: Removing the SHA512 hash simplifies the packageManager field, making it easier to update the package manager version in the future. While it reduces integrity checks, the trade-off for maintainability is reasonable.	6

[github-actions]

Bundle Size

Status	File	Size (Gzip)	Limits
✅	index.js	14.3 KB	15 kb

Overall bundle size: 14.3 KB
Overall status: ✅