Removing an environment from a lifecycle can continue displaying old releases on a project's Deployments page

[KennethBates]

Severity

One report

Version

https://octopus.com/downloads/2024.2.4636

Latest Version

None

What happened?

If you remove an environment from a lifecycle, a project that uses that lifecycle can still potentially be displaying old releases on its Deployments page. This looks to be due to the older releases being displayed still being considered "latest" in the now-removed environment in the dashboard's display logic, and still shows it to environments still within the current lifecycle because of this.

Reproduction

Deploy a release to the first two environments in a project's lifecycle Deploy a few more just to the second environment (enough to fall outside of the amount the dashboard calculates for displaying on the Deployments page) Remove the first environment from the lifecycle See the old release still displaying in the column for the second (now first) environment, even though there have been deployments of releases between that and what is above it.

In my reproduction (link below), this is version 0.0.2, which should not be displayed (as 0.0.3 & 0.0.4 are newer and have been successfully deployed to this environment)

Repro project link

Error and Stacktrace

No response

More Information

Reported here (private):

Workaround

Delete these old releases or deployments to this now-removed environment.