Recommended Workflow and Best Practices for Version Upgrades in MercurJS Projects

[furkankarakuzu]

Hello MercurJS Team,

I am currently working on a project built with MercurJS and I would like to get your expert advice on the official/recommended way to handle version upgrades for both Medusa core and MercurJS-specific packages.

While my current setup (based on Medusa 2.8.6 and MercurJS * wildcards) is stable, I encounter significant TypeScript and build issues when attempting to bump the Medusa core versions (e.g., upgrading to 2.11.x).

My Question: Rather than focusing on a specific version, what is the general recommended workflow for keeping a MercurJS project up to date? Specifically:

The "Official" Way: Since MercurJS is a sophisticated starter/boilerplate rather than just a library, should we follow an upstream merge strategy from the main repo, or is it intended to be managed solely via package.json updates?

Type Synchronization: After updating @medusajs/* or @mercurjs/* dependencies, what is the correct sequence of commands to ensure that the generated types in the .medusa folder align with the new versions?

Core Extraction vs. In-place Update: Do you recommend migrating custom logic (src/api, src/modules, src/workflows) to a fresh create-mercur-app skeleton for major version jumps, or is there a way to safely update the existing structure?

Handling Wildcards: Given that @mercurjs/* packages are often set to *, how can we ensure compatibility when the underlying Medusa framework introduces breaking changes in its minor releases?

Current Context (as an example): I am currently attempting to move from Medusa 2.8.6 to 2.11.3, but the question is aimed at establishing a long-term maintenance routine for any future release.

Any documentation, CLI tools, or specific scripts you recommend for a smooth migration process would be extremely helpful for the community.