Duplicate commits and work items are contributed to deployment changes

[shaun-od]

Severity

No response

Version

Probably since Build Information was introduced

Latest Version

I could reproduce the problem in the latest build

What happened?

Duplicate commits and work items from build information can be added to a deployment record when a project contains releases that have not been deployed from the last deployment.

Reproduction

1. Create a deployment process that references packages.
2. Add build information to those packages that contain commits (and if you want work items references a work item Fixes #1 with a work issue tracker enabled.
3. Create a release and deploy it to an environment.
4. Create 1 or more releases with a version numbers that are after the first release, and don't deploy them.
5. Create another release with a version number later than all the above releases and deploy it

The deployment for the last release will contain duplicate commit and work items

Error and Stacktrace

No response

More Information

No response

Workaround

No response

[octoreleasebot]

Release Note: Release changes in a single deployment record no longer contain duplicate commit and work items for a package.

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2024.2	2024.2.7747
2024.3+	all releases