feat(util/template): add prettyVersion field

[hasanwhitesource]

Changes

Exposed a handlebars function to enable prettifying newVersion and newMajor.

Context

Closes #13299

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 tick 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

[hasanwhitesource]

@HonkingGoose what do you think of the docs change ?

[astellingwerf]

May I suggest you update the PR title to 'prepend' instead of 'append'?

[rarkins]

How does this compare in ease of use to just using a replace helper? Or does it not support regex ^?

[hasanwhitesource]

How does this compare in ease of use to just using a replace helper? Or does it not support regex ^?

You mean to expose a function to users that replaces strings ?

[rarkins]

We already expose a replace function

[rarkins]

Why not the prettyX strings we discussed previously? If it's a common use case then let's just prepopulate them

[hasanwhitesource]

@rarkins It is the same as we discussed in the issue I just named it prettifyVersion so it can be used like this :

{
    "semanticCommits": "enabled",
    "commitMessageAction": "",
    "commitMessageTopic": "{{depName}}",
    "commitMessageExtra": "{{prettifyVersion newVersion}}"
}

or on newMajor

{
    "semanticCommits": "enabled",
    "commitMessageAction": "",
    "commitMessageTopic": "{{depName}}",
    "commitMessageExtra": "{{prettifyVersion newMajor}}"
}

[rarkins]

Why not just prettyVersion etc? I don't think we discussed which is better for the end user or maintainability

[rarkins]

Plans for prettyNewMajor too?

[viceice]

otherwise LGTM

[renovate-release]

🎉 This PR is included in version 32.152.0 🎉

The release is available on:

• GitHub release
• 32.152.0

Your semantic-release bot 📦🚀