`minimumReleaseAge` configuration in `recommended.json` interferes with Git submodules

[bkeryan]

Renovate 42 changed the behavior of minimumReleaseAge: renovatebot/renovate#39133

Now this feature requires a release timestamp by default.

The git-submodules manager uses the git-refs data source, which does not provide a release timestamp.

This results in a pending renovate/stability-days check which never completes:

Perhaps we should do one of the following:

• Only set minimumReleaseAge for specific managers / data sources
• Disable minimumReleaseAge for git-submodules
• Set minimumReleaseAgeBehaviour=timestamp-optional for specific managers / data sources

[bkeryan]

I have also seen a pending renovate/stability-days check for lockFileMaintenance.

https://docs.renovatebot.com/key-concepts/minimum-release-age/ says

The lockFileMaintenance update type does not provide release timestamps, as the package manager performs the required changes to update package(s).

This is weird because the release timestamps are available from the pypi data source. But lockFileMaintenance doesn't actually use Renovate's pypi or npm data source, I think it just reruns the lock tool and updates everything to the latest.

https://docs.renovatebot.com/presets-security/#securityminimumreleaseagenpm disables minimumReleaseAge for lockFileMaintenance:

    {
      "description": "Do not require Minimum Release Age for update types that are controlled by the package manager",
      "matchDatasources": [
        "npm"
      ],
      "matchUpdateTypes": [
        "lockFileMaintenance"
      ],
      "prBodyNotes": [
        "⚠️ Renovate's lock file maintenance functionality does not support validating Minimum Release Age, as the package manager performs the required changes to update package(s). Confirm whether your package manager perform its own validation for the Minimum Release Age of packages."
      ],
      "minimumReleaseAge": null
    },