Master Task: Keep Dependencies Up-to-Date

This section is used to track and coordinate dependency updates across the entire project.

Keeping our dependencies up-to-date is important for:

• ✅ Security patches – Fix vulnerabilities and keep the project safe
• 🚀 Performance improvements – Take advantage of faster and more optimized code
• 🧼 Better maintainability – Reduce tech debt and avoid outdated code
• 🧪 Tooling compatibility – Ensure support for the latest frameworks, plugins, and build tools

🔄 Ongoing Upgrade Process

We follow a regular workflow to manage and apply dependency updates:

• Monitor new releases of important libraries and tools
• Prioritize updates that include critical fixes or breaking changes
• Create separate issues for major package upgrades (e.g., react, webpack)
• Review changelogs and official migration guides before upgrading
• Test thoroughly after updates to ensure nothing breaks
• Document progress and keep this section up to date

🛠️ Tools & Automation

To make this process easier and more reliable, we use the following tools:

• ✅ pnpm outdated or npm-check-updates – Check which packages are outdated
• ✅ GitHub automation tools:
  • Renovate
  • Dependabot
  • Custom GitHub Actions (if needed)
• ✅ Manual checks for major or breaking changes

🔁 Note: This is an ongoing process. This section will remain in the README as a reference and reminder to regularly update and review dependencies.

Start with the README section described in this issue and inspect the project's package manifests and existing automation. Review the dependency-update tools and migration guidance named here; this is complete only when a specific update plan or separate upgrade issues are documented and the tracking section reflects current progress.