Upgrade > Package deployment behavior post upgrade

Package deployment behavior post upgrade

After you upgrade Codar from 1.50 or 1.60 to 1.70, the lifecycle stage of an existing Instance for package deployment will be set to DEVELOPMENT by default, regardless of its lifecycle stage prior to the upgrade. Therefore, even if a package had an instance that was deployed in production stage prior to the upgrade, it cannot be published post upgrade directly. The package must be deployed once again in PRODUCTION stage, and only then can it be published.