Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Reployments should include package metadata from last successful deployment #5614
In the design of the package metadata features the deployments quite deliberately builds the list of changes from each release between the one that was last deployed to a scope (env/tenant) and the current deployment. So it's building the "delta" of what is changing between when the deployment started and when it completed.
This all holds and makes sense when you are deploying a new version to an environment. However, when you redeploy things aren't what you may think/expect. The current implementation determines that there is no delta, because the version is the same, and therefore no package metadata/work items etc are included.
This enhancement is to include the package metadata from the release(s) from the previously successful deployment. It will be important to take the details from the release, rather than the previous deployment itself, otherwise when we implement #5605 the result of the redeploy would be the old details and not the current details.