Olivier Vernin

For information you need a Jenkinsfile similar to [jenkins-infra/docker-helmfile](https://github.com/jenkins-infra/docker-helmfile/blob/main/Jenkinsfile_k8s) and then modify the sharedlibrary [here](https://github.com/jenkins-infra/pipeline-library/blob/master/vars/buildDockerAndPublishImage.groovy) to also push to ghcr. In the back it uses this [makefile](https://github.com/jenkins-infra/pipeline-library/blob/master/resources/io/jenkins/infra/docker/Makefile) which shouldn't be...

I am considering working on the current issue as It could simplify the autodiscovery manifest by not having to specify scm or action configuration. Right now I see two ways...

Thanks for your feedback, I am also more in favor of the second approach. I'll try to find some time to dig into it

I now remember when I implemented the docker digest plugin, I hesitated either that result should or should not contains the '@' and apparently, you think I was wrong :)...

Looking at the code today, your suggestion make sense to me

I am curious how ideally you would like use the digest information. As @dduportal remind me, the way we use dockerdigest on the Jenkins project, is by removing "sha256" anyway...

Thanks for reporting, I thought that everything was updated. I'll keep an eye on this issue when I merge long running pullrequest

I had a look to the issue and you are right, the description is never updated as defined [here](https://github.com/updatecli/updatecli/blob/5c92704948b80a787abfbbbcf787b365236d83b4/pkg/core/reports/actionTarget.go#L4) Similar to changelog I should have a list but I still...

Theoretically this issues should be fixed by https://github.com/updatecli/updatecli/pull/2021 And more specifically in https://github.com/updatecli/updatecli/blob/951bc936b8177ed559422a7ebd0d6a7636e97b73/pkg/plugins/scms/github/pullrequest.go#L571 where I revert the order of the merge action so the new report should take precedence over...

The alternative is to have a specific policy for Golang version update