feat: dockercompose autodiscovery handles digest #1932
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Olblak <me@olblak.com>
olblak
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Similar pullrequest than #1931
Now by default the Dockercompose autodiscovery plugin will insert a digest unless the parameter digest is set to false.
This feature now allows the following update
updatecli/updatecli:latesttoupdatecli/updatecli:latest@sha256xxxxupdatecli/updatecli:0.23.0toupdatecli/updatecli:0.73.0@sha256xxxupdatecli/updatecli:0.73.0@sha256xxxtoupdatecli/updatecli:0.73.0@sha256yyyI also took the opportunity to update the generated template for using conventional commits messages like
deps(dockercompose): bump image "updatecli/updatecli" digestTest
To test this pull request, you can run the following commands:
Additional Information
Tradeoff
Potential improvement