Olivier Vernin

> I tried this on https://github.com/jenkinsci/bom > > The formatting of the file gets broken really badly after apply: Indeed, sorry about that. I opened a bug on the project...

At this stage source and condition are working as expected but additional work is still needed for the target stage. Considering that I am mainly interested by the target at...

Closing in favor of https://github.com/updatecli/updatecli/pull/823

I recently had a look to this plugin and I think the only way to solve this is by doing a git diff on the Chart.yaml. Because the problem also...

I am currently working on a new Updatecli feature, named "autodiscovery". The goal of the autodiscovery is to generate manifest based on a context. So by default running `updatecli apply/diff/show`...

Now that the xml resource is released ([0.32.0](https://github.com/updatecli/updatecli/releases/tag/v0.32.0)), ready and working quite well on my project. I started thinking to the current issue but I don't think I am understanding...

I opened a draft pullrequest here https://github.com/updatecli/updatecli/pull/833 Right now it only support "dependencies" > Does it support reading a parent pom ? Do you mean updating something like this https://github.com/jenkins-infra/pipeline-steps-doc-generator/blob/master/pom.xml#L4L8...

The way the autodiscovery works is either you provide no configuration such `./bin/updatecli diff --experimental `: In this case it search locally and recursively available updates but no scm support...

The pullrquest is now ready and support the following cases 1. Read pom.xml looking and try to bump version in `/project/parent` if a version is specified and do not contains...

I like this idea very much