CRM Analytics Version History does not Change When Migrated

This is a product limitation. Salesforce updates the version history only through the Connect API, not the Metadata API. The Metadata API doesn't modify the history tables.

Note: This applies Not only to Recipes but also to Dashboards and Dataflows.

One possible solution (manual) is to re-save the recipe.

Re-saving a recipe in the target org will create a new version history entry for that environment, but it does not restore historical versions from the source org. This workaround is useful only when you need to establish a baseline version in the new environment. The root cause is that version history is written by the Connect API (used during interactive saves) and is not replicated by the Metadata API used during deployments.