Package Retention Issue: Packages Using Variable-Based Package IDs Purged Despite Active Releases

[HuyPhanNguyen]

Severity

No response

Version

2025.1.5569

Latest Version

I could reproduce the problem in the latest build

What happened?

Packages that are referenced using variable-based package IDs in steps are being purged from the built-in feed despite being actively referenced by releases and deployments. The system is not maintaining the package-to-release association for packages whose IDs are calculated via variables.

Example case: This internal ticket

• Release 250108.1.1000092+main.0a835c8.92.docker was created on Jan 8th, 16:45
• Release was deployed to Production Proxy environment on Jan 8th, 16:46
• Package was purged from internal feed on Jan 10th, 18:03
• The release still shows as active on the Deployments page

Reproduction

1. Create a project with steps that use variable-based package IDs (e.g., in step templates)
2. Create a release specifying package versions
3. Deploy the release to any environment
4. Set package retention to 1 day
5. Wait for 2 day and trigger the built-in feed's retention period
6. Observe that the package is purged despite being referenced by an active deployment

Expected Behavior

• Packages referenced via variable-based package IDs should be retained while the release is active
• Package-to-release association should be established at release creation time when versions are specified
• Variable-based package references should be treated the same as static package references for retention

Actual Behavior

• Packages referenced via variables are purged by package retention regardless of associate with a release
• System fails to maintain package-to-release associations for variable-based package IDs
• Releases become non-deployable after package purge despite being "active"

Workaround

• Set retention policy to bigger value or Forever