Context
The Publish-PSModule workflow includes a prerelease cleanup step that removes old prerelease versions after a stable release. The cleanup notice currently only shows the count of removed prereleases, not which specific versions were removed.
Request
When prerelease versions are cleaned up during the publish workflow, the notice displays only a count:
Cleaned up 7 prerelease(s) for [caketest].
There is no visibility into which specific prerelease versions were removed. This makes it difficult to audit or debug if a prerelease was removed unexpectedly.
What is expected
The cleanup notice should list the specific prerelease versions that were removed:
Cleaned up 7 prerelease(s) for [caketest]:
- 0.1.0-preview.1
- 0.1.0-preview.2
- 0.1.0-preview.3
- 0.2.0-alpha.1
- 0.2.0-alpha.2
- 0.2.0-beta.1
- 0.2.0-beta.2
Acceptance criteria
- The cleanup notice includes the list of removed prerelease version strings
- The notice remains readable even when many prereleases are removed
- Existing cleanup behavior is not affected
Technical decisions
To be determined during implementation planning.
Implementation plan
Context
The Publish-PSModule workflow includes a prerelease cleanup step that removes old prerelease versions after a stable release. The cleanup notice currently only shows the count of removed prereleases, not which specific versions were removed.
Request
When prerelease versions are cleaned up during the publish workflow, the notice displays only a count:
There is no visibility into which specific prerelease versions were removed. This makes it difficult to audit or debug if a prerelease was removed unexpectedly.
What is expected
The cleanup notice should list the specific prerelease versions that were removed:
Acceptance criteria
Technical decisions
To be determined during implementation planning.
Implementation plan