Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All non-major group now containing Docker tags suffix #17366

Closed
setchy opened this issue Aug 23, 2022 · 7 comments · Fixed by #17381 or #17383
Closed

All non-major group now containing Docker tags suffix #17366

setchy opened this issue Aug 23, 2022 · 7 comments · Fixed by #17381 or #17383
Labels
status:requirements Full requirements are not yet known, so implementation should not be started type:bug Bug fix of existing functionality

Comments

@setchy
Copy link
Collaborator

setchy commented Aug 23, 2022

How are you running Renovate?

Mend Renovate hosted app on github.com

If you're self-hosting Renovate, tell us what version of Renovate you run.

No response

Please select which platform you are using if self-hosting.

No response

If you're self-hosting Renovate, tell us what version of the platform you run.

No response

Was this something which used to work for you, and then stopped?

It used to work, and then stopped

Describe the bug

In the last few days I've noticed a number of our non-major dependency PRs now containing a suffix of Docker tags which I haven't noticed before.

I've created a minimal reproduction repository here - https://github.com/setchy/renovate-minor-group-name/pull/1

Of note is this PR contains both a Dockerfile and pom.xml update, yet has the Docker tags string appended to the group name

I'm not sure if there is any correlation with moving to the renovate:slim image and using RENOVATE_BINARY_SOURCE=install

Relevant debug logs

Logs
Copy/paste the relevant log(s) here, between the starting and ending backticks

Have you created a minimal reproduction repository?

I have linked to a minimal reproduction repository in the bug description

@setchy setchy added priority-5-triage status:requirements Full requirements are not yet known, so implementation should not be started type:bug Bug fix of existing functionality labels Aug 23, 2022
@setchy
Copy link
Collaborator Author

setchy commented Aug 23, 2022

Update: just tested with a self-hosted configuration using the docker image renovate/renovate and RENOVATE_BINARY_SOURCE=global and the PR name remains the same

@viceice
Copy link
Member

viceice commented Aug 24, 2022

This is caused by #17102, which fixed a bug where the docker datasource defauzlt config was never applied. So this is an expected behavior to me.

So you would need to override commitMessageTopic for your group. 🤔

@rarkins WDYT?


const defaultConfig = {
commitMessageTopic: '{{{depName}}} Docker tag',
commitMessageExtra:
'to {{#if isMajor}}{{{prettyNewMajor}}}{{else}}{{{prettyNewVersion}}}{{/if}}',
digest: {
branchTopic: '{{{depNameSanitized}}}-{{{currentValue}}}',
commitMessageExtra: 'to {{newDigestShort}}',
commitMessageTopic:
'{{{depName}}}{{#if currentValue}}:{{{currentValue}}}{{/if}} Docker digest',
group: {
commitMessageTopic: '{{{groupName}}}',
commitMessageExtra: '',
},
},
pin: {
commitMessageExtra: '',
groupName: 'Docker digests',
group: {
commitMessageTopic: '{{{groupName}}}',
branchTopic: 'digests-pin',
},
},
group: {
commitMessageTopic: '{{{groupName}}} Docker tags',
},
};

@viceice
Copy link
Member

viceice commented Aug 24, 2022

maybe we should update group:allNonMajor preset to override commitMessageTopic ? 🤔

@setchy
Copy link
Collaborator Author

setchy commented Aug 24, 2022

maybe we should update group:allNonMajor preset to override commitMessageTopic ? 🤔

ah, so it's lines 365 to 367 thats introduced this new commit message.

Could that be removed and just rely on the groupName? I'd imagine similar outcomes would happen for many of the other group presets, not just group:allNonMajor

@rarkins
Copy link
Collaborator

rarkins commented Aug 24, 2022

The only other place we've specified commitMessageTopic for group is in Helm, and that was probably copied from Docker. I think it may be easier to remove those lines.

@setchy
Copy link
Collaborator Author

setchy commented Aug 24, 2022

#17381

@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 32.174.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:requirements Full requirements are not yet known, so implementation should not be started type:bug Bug fix of existing functionality
Projects
None yet
4 participants