Added
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.188.0...v0.189.0
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.188.0...v0.189.0
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.187.2...v0.188.0
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.187.1...v0.187.2
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.187.0...v0.187.1
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.186.1...v0.187.0
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.186.0...v0.186.1
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.185.2...v0.186.0
Releases 1.72.5 – 1.72.9 never reached any installation. push-to-registries timed out pushing the image across the Pacific to the Aliyun registry on every one of those tags, which blocked launch-container and therefore push-happa-to-catalog. The images were fine and present in gsoci, but the chart never published, so the OCIRepository (semver: x.x.x) had nothing newer than 1.72.4 to pick up. GitHub showed green releases throughout, so this was invisible.
This release fixes that and carries the whole backlog — 66 commits since 1.72.4, including roughly ten security-only dependency updates that had been merged and released but never deployed.
split-china-push) and a separate sync-china-registry job mirrors to Aliyun from the in-China runner, with nothing depending on it (#4881).Full diff: https://github.com/giantswarm/happa/compare/v1.72.4...v1.72.10
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.185.1...v0.185.2
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.185.0...v0.185.1