Allow forcing the use of the generic updater in extra-files
#2205
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Is your feature request related to a problem? Please describe.
Since #2072, any JSON, XML, YAML or TOML file is updated using their corresponding updater, meaning that the value of a top level
version
key, if existing, is bumped. It should be possible to override this default behavior.My use case is to bump a docker image tag in a
docker-compose.yaml
file, that contains a top-levelversion
key, like such:I tried two things:
When using this config, the
version: "3.8"
is replaced byversion: v0.1.1
, and theimage
value is left untouched.When using this second config, the
image
value is transformed tov0.1.1
, deleting themy-org/my-repo:
part.Describe the solution you'd like
Allow something like this, that won't attempt to modify the top-level
version
:Describe alternatives you've considered
As specified there, the
version
key is not strictly necessary for a docker-compose file, so removing this key leads to the desired behavior. However, this is only a temporary workaround.The text was updated successfully, but these errors were encountered: