Date field is now disallowed

[robin-moss]

How are you running Renovate?

Self-hosted

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

25.48.0

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

GitLab self-hosted

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

whitesource/renovate:1.5.0

Describe the bug

We have the following template for a commitBody configuration: "{{# logJSON.versions}} ## [{{version}}]({{releaseNotes.url}}) {{date}}\n{{releaseNotes.body}}\n{{/logJSON.versions}}" that was working, but recently we've started to get a Disallowed variable name in template

I can see this is being raised from the check in here but I don't know why the date field so no longer allowed

Relevant debug logs

"varName": "date",
"template": "{{# logJSON.versions}} ## [{{version}}]({{releaseNotes.url}}) {{date}}\n{{releaseNotes.body}}\n{{/logJSON.versions}}",
"msg": "Disallowed variable name in template"

Have you created a minimal reproduction repository?

No reproduction repository

[robin-moss]

Looks like it's related to this PR

[rarkins]

Available fields are listed in https://docs.renovatebot.com/templates/

Anything else you like, please submit a feature request including reproduction repo to test against

[viceice]

Here is the source:

renovate/lib/util/template/index.ts

Lines 66 to 127 in 7770888

	export const allowedFields = {
	baseBranch: 'The baseBranch for this branch/PR',
	body: 'The body of the release notes',
	currentValue: 'The extracted current value of the dependency being updated',
	currentVersion:
	'The version that would be currently installed. For example, if currentValue is ^3.0.0 then currentVersion might be 3.1.0.',
	datasource: 'The datasource used to look up the upgrade',
	depName: 'The name of the dependency being updated',
	depNameLinked:
	'The dependency name already linked to its home page using markdown',
	depNameSanitized:
	'The depName field sanitized for use in branches after removing spaces and special characters',
	depType: 'The dependency type (if extracted - manager-dependent)',
	displayFrom: 'The current value, formatted for display',
	displayTo: 'The to value, formatted for display',
	hasReleaseNotes: 'true if the upgrade has release notes',
	isLockfileUpdate: 'true if the branch is a lock file update',
	isMajor: 'true if the upgrade is major',
	isPatch: 'true if the upgrade is a patch upgrade',
	isPin: 'true if the upgrade is pinning dependencies',
	isRollback: 'true if the upgrade is a rollback PR',
	isReplacement: 'true if the upgrade is a replacement',
	isRange: 'true if the new value is a range',
	isSingleVersion:
	'true if the upgrade is to a single version rather than a range',
	logJSON: 'ChangeLogResult object for the upgrade',
	lookupName: 'The full name that was used to look up the dependency.',
	newDigest: 'The new digest value',
	newDigestShort:
	'A shorted version of newDigest, for use when the full digest is too long to be conveniently displayed',
	newMajor:
	'The major version of the new version. e.g. "3" if the new version if "3.1.0"',
	newMinor:
	'The minor version of the new version. e.g. "1" if the new version if "3.1.0"',
	newName:
	'The name of the new dependency that replaces the current deprecated dependency',
	newValue:
	'The new value in the upgrade. Can be a range or version e.g. "^3.0.0" or "3.1.0"',
	newVersion: 'The new version in the upgrade, e.g. "3.1.0"',
	packageFile: 'The filename that the dependency was found in',
	packageFileDir:
	'The directory with full path where the packageFile was found',
	parentDir:
	'The name of the directory that the dependency was found in, without full path',
	platform: 'VCS platform in use, e.g. "github", "gitlab", etc.',
	prettyDepType: 'Massaged depType',
	project: 'ChangeLogProject object',
	recreateClosed: 'If true, this PR will be recreated if closed',
	references: 'A list of references for the upgrade',
	releases: 'An array of releases for an upgrade',
	releaseNotes: 'A ChangeLogNotes object for the release',
	repository: 'The current repository',
	semanticPrefix: 'The fully generated semantic prefix for commit messages',
	sourceRepoSlug: 'The slugified pathname of the sourceUrl, if present',
	sourceUrl: 'The source URL for the package',
	updateType: 'One of digest, pin, rollback, patch, minor, major, replacement',
	upgrades: 'An array of upgrade objects in the branch',
	url: 'The url of the release notes',
	version: 'The version number of the changelog',
	versioning: 'The versioning scheme in use',
	versions: 'An array of ChangeLogRelease objects in the upgrade',
	};

[robin-moss]

It sounds like despite this field being part of logJSON.versions the check does not allow us to use the date field, if I wanted you to add support for it I need to create a repo to demonstrate this and create a feature request.

In which case we'll stick with removing the field, we work in a self-hosted corporate environment and I don't have a setup for using renovate in a public capacity

[HonkingGoose]

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

25.48.0

You're multiple versions behind, I recommend you update your version of Renovate. 😉

[robin-moss]

Even if we upgrade the date field is still missing, even though it's part of the logJSON.versions object

[rarkins]

You won't get support in this forum for old versions in future.

[maxiangelo]

Why is there the option for isMajor and isPatch but not isMinor? @robin-moss @rarkins

[github-actions[bot]]

Hi there,

This is intended as a polite, automated request that users avoid @ mentioning repository maintainers like @rarkins or @viceice. Doing so causes annoying mobile notifications and makes it harder to maintain this repository.

We know it might be common elsewhere but we participate in hundreds of discussions a week and would need to turn off GitHub mobile notifications if we were mentioned in every one.

As a general rule, we will read and respond to all discussions in this repository, so there is no need to mention us.

Thanks, the Renovate team