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

Thank you for following the naming conventions for pull request titles! 🙏

The PR shows a downgrade of the "next" package from version "13.5.5" to "13.4.19". If this downgrade is intentional, please ensure that it doesn't break any existing functionality that relies on features or fixes introduced in the newer version. If it's not intentional, I would suggest keeping the package up-to-date. Here's the suggested change:

-    "next": "13.4.19",
+    "next": "13.5.5",

Please make sure to test the application thoroughly after making this change.
The PR seems to be updating the versions of various dependencies in the pnpm-lock.yaml file. Here are a few suggestions:

1. Ensure that the updated versions of the dependencies are compatible with the rest of the codebase. This can be done by running all the tests after the dependencies have been updated.

2. It's a good practice to check the changelogs of the updated dependencies to understand what has changed. This can help identify potential issues that could arise from the update.

3. Consider using a tool like Dependabot to automate dependency updates. This can help keep your dependencies up-to-date and reduce the manual work of updating them.

4. Make sure to thoroughly test the application after updating the dependencies to ensure everything still works as expected.

5. It's a good practice to update dependencies in small batches. This makes it easier to identify which update caused a problem if one arises.

6. If a dependency is not being used in the project, consider removing it to reduce the complexity and potential security vulnerabilities of your project.

7. If the project is using a continuous integration (CI) service, make sure that the CI build passes after the dependencies have been updated.