IR-468: blocked-edges/4.15.8-AzureRegistryImageMigrationUserProvisioned: Fixed in 4.15.9 #5120
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The buggy Secret handling is still present in 4.15.9, but it is present in all 4.15.z so far, so no regressions for 4.15-to-4.15 updates. And 4.14.(>=15) are exposed, so both sides of 4.14.(>=15) to 4.15 are exposed, and no regressions there either. That leaves 4.14.(<15) to 4.15, and while we have those up through 4.14.8, 4.14.9 was built after 37826e2 (#5052) merged, and there are no 4.14.(<15) to 4.15.(>=9) edges to talk about.