There are two ways of handling versioning in Micro-Frontends, the "evergreen" approach which is the traditional "use the latest" deployed version in production and the "managed" approach where you keep previous versions and use semantic versioning (similar to dependencies). The advantages of the "managed" approach are that you can quickly hot-swap, roll back and run A/B experiments with your Micro-Frontends.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There are two ways of handling versioning in Micro-Frontends, the "evergreen" approach which is the traditional "use the latest" deployed version in production and the "managed" approach where you keep previous versions and use semantic versioning (similar to dependencies). The advantages of the "managed" approach are that you can quickly hot-swap, roll back and run A/B experiments with your Micro-Frontends.