Breaking changes in images

[molexx]

A recently deployed change to docker compose in the Ubuntu image has broken, as can be seen by the mentions, A LOT of projects:

#9692

As mentioned in comments in the above, users are prepared for breaking changes in new images but not in updates to existing images. Investigating and fixing costs everyone time and those who rely on GitHub Actions for production deployments could be severely impacted which makes this a business risk.

It seems there is no way to 'pin' an image version and creating a custom image seems more effort than should be necessary. Personally I'm not particularly interested in better announcements, that would still cost us time, I just want our builds to keep working. It should be up to teams and their businesses to balance the risks and decide when to spend resource on updating - like we do with all our libraries and tools.

Perhaps you could reconsider reserving breaking changes for new images?
Or offering a way to pin specific versions?
Or offering an 'LTS' image that never has breaking changes?

Thank you.