Resolve version mismatch in ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure
Deployment from staging to production fails if the ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure version in staging is older than in production. This mismatch can trigger compatibility issues and block deployments. Aligning environment versions or resetting production can resolve the issue and ensure smooth deployment.
Description description
Environment
- ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure
- Pro Staging / Production clusters
Issue/Symptoms
- Deployment pipeline fails when pushing code from staging to production.
- Logs indicate that the failure is caused by an attempt to downgrade the ÃÛ¶¹ÊÓƵ Commerce version in production.
- Compatibility issues arise due to differing versions between staging and production environments.
Resolution resolution
Note:
Before proceeding with environment resets or database changes, ensure you have a complete and validated backup of your production environment. You can use the snapshot functionality to create and manage backups safely.
To resolve this issue, ensure that all environments are aligned with the same ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure version as production. Follow these steps:
- Upgrade the staging environment to match the version used in production. This ensures consistency across environments and prevents deployment failures. For more information, refer to Upgrade Commerce version.
- If upgrading staging is not feasible, consider resetting the production environment to match staging. Confirm that a backup has already been taken before proceeding. Obtain permission to drop the existing production database if necessary. For more information, refer to Reset environment on ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure.
- Remove configuration files (
config.php) from your repository temporarily:- This disables configuration management during reset operations. For more information, refer to Roll back environment without Cloud snapshot.
- Uninstall ÃÛ¶¹ÊÓƵ Commerce software using the setup:uninstall Ìý³¦´Ç³¾³¾²¹²Ô»å:
- Ensure all previous configurations are cleared before redeployment. For more information, refer to Uninstall ÃÛ¶¹ÊÓƵ Commerce.
- Redeploy your codebase after aligning versions or resetting environments:
- Include
composer.lockin your repository commits for proper dependency management.
- Include
- Verify that all changes are applied successfully and confirm functionality post-deployment.
By maintaining consistent versions across all environments or resetting incompatible setups, you can ensure smooth deployments without encountering compatibility issues.