Remove/enable suppression of minimumReleaseAgeBehaviour=timestamp-optional warning

[morremeyer]

Tell us more.

We have intentionally set minimumReleaseAgeBehaviour to timestamp-optional so that we get the benefits of minimum release age where possible, but don't block updates for everything else.

For every repository where at least one release does not have a timestamp, we now get the following warning in the dependency dashboard:

⚠️ WARN: Some release(s) did not have a releaseTimestamp, but as we're running with minimumReleaseAgeBehaviour=timestamp-optional, proceeding. See debug logs for more information

Since we have intentionally set this configuration, we don't want this warning to appear. I would even argue that since the default configuration is timestamp-required, this warning is counterproductive:

It is telling the user about an option they explictly set, contributing to alert fatigue since it's another warning that needs to be ignored.

I suggest to either allow to disable it, or better, entirely remove it.

[jamietanna]

While true that you know you've set this, it's not always the case that everyone is aware.

The issue is where there may be shared presets / self-hosted configuration that applies it, and then end-users aren't aware of it, so getting a warning to inform them is - IMO - reasonable.

That being said, logLevelRemap is what you'll want here in the meantime of us deciding as to whether we want to add i.e. minimumReleaseAgeBehaviour=timestamp-optional,omit-warning

[morremeyer]

No day passes where I learn something new about what renovate can do. Thank you!

With remapping being available, this might also just be a documentation update: Adding that this is intentional, and can be remapped.

[jamietanna]

Trust me, I'm always finding out new things too 😹

[jamietanna]

Docs improvement welcome!