What werf/werf shipped
Generated by FoxPlug from public activity — not affiliated with Werf.
Week of September 14, 2026
What shipped
- Cleanup now preserves final images correctly when stages are published to both primary and final repositories. Pull request #7867
- GitLab registry cleanup uses the supported manifest-by-tag API instead of falling back to slower digest deletion. Pull request #7866
- Deploy renders included charts at the project root correctly when `deploy.helmChartDir: .` is configured. Pull request #7865
- ReleaseInstall now returns rendered resources from the deploy operation. Pull request #7869
- Build reports now include the werf version that produced them for easier tracking across CI runs. Pull request #7859
- Deploy prevents panics when release deletion fails. Pull request #7861
Why it matters
This week addresses cleanup correctness for dual-repository setups, improves registry performance for GitLab users, and fixes deploy rendering with included charts. Build reports are now more traceable with version information included.
Changelog entry
- feat(deploy): return rendered resources from ReleaseInstall Pull request #7869
- fix(deploy): render included charts at the project root Pull request #7865
- fix(cleanup): preserve retained final images when stages are published to both repo and final-repo Pull request #7867
- fix(cleanup): avoid slow tag deletion in GitLab registries by preferring manifest-by-tag API Pull request #7866
- feat(build): include werf version in the build report Pull request #7859
- fix(deploy): prevent panic when release deletion fails Pull request #7861
Werf now preserves final images correctly in cleanup, speeds up GitLab registry operations, and fixes chart rendering for includes. Build reports include version info for better traceability.
This week's werf updates focus on cleanup reliability and registry performance. Final images are now properly retained in dual-repository setups, GitLab cleanup operations are faster with the manifest-by-tag API, and Helm chart rendering works correctly with includes at the project root. Build reports now include version information for improved traceability across CI runs.