This is a follow-up to #9365. Since our Dockerfiles now have a hardcoded full version of .NET and an image digest for reproducible builds, we need a way to automate their update. Doing it manually is error-prone and prone to forgetting, which may cause unpredictable issues later.

Changes

• Added a new workflow to update Dockerfiles with the latest digests and versions available. It creates a PR with changes, if any.
• The workflow runs automatically every midnight. Such a frequency is needed to be on par with that of GitHub Actions. If required, it can be triggered manually as well.

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Notes on testing

Tested manually