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

Open
#6 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
git
Domain
devops

Research direction

Start by reading recommended.json and checking how its minimumReleaseAge settings apply to the git-submodules manager and git-refs data source. Compare the configuration options listed in the issue, then verify the chosen change prevents the renovate/stability-days check from remaining pending when no release timestamp is available.

Written by the indexing model from the issue text.

Description

bug

Renovate 42 changed the behavior of minimumReleaseAge: https://github.com/renovatebot/renovate/discussions/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:

Image

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
Dominant language
No language data
Stars
0
Forks
2
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ni/python-renovate-config

All issues in ni/python-renovate-config

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.