feat(templates): allow upgrades in commitMessage and prTitle

[amezin]

Changes

Allow access to upgrades in commitMessage and prTitle templates.

Context

#29546

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

Can you refactor this into a function first (with no functional changes), and then after apply this change?

[amezin]

It seems that existing tests didn't verify hasBaseBranches: true and separateMajorMinor: true cases (there are such updates in the tests, but their generated title was always thrown away and not checked)

[rarkins]

Can you link to the repository you tested against? I think we need to validate both the group and non-group cases

[amezin]

Can you link to the repository you tested against? I think we need to validate both the group and non-group cases

https://github.com/amezin/renovate-template-issues

[rarkins]

Awaitinv v38

[amezin]

Do you consider this to be a breaking change?

Should I switch the target branch to v38?

approval

[renovate-release]

🎉 This issue has been resolved in version 38.2.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 38.2.0

Your semantic-release bot 📦🚀