PR opened and then auto closed 8 hours later

[ReenigneArcher]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

No response

Please tell us more about your question or problem

LizardByte/actions#245

Why was it autoclosed, and why did it take 2 weeks to open the PR to begin with. Any ideas?

Logs (if relevant)

Logs

DEBUG: Value is not updated (branch="renovate/pytest")
{
  "depName": "pytest",
  "manager": "pep621",
  "packageFile": "actions/setup_python/pyproject.toml",
  "expectedValue": "==9.1.1",
  "foundValue": "==9.0.3"
}

DEBUG: exec completed (branch="renovate/pytest")
{
  "durationMs": 668,
  "stdout": "",
  "stderr": "Using CPython 3.14.6 interpreter at: /opt/containerbase/tools/python/3.14.6/bin/python3\nResolved 7 packages in 48ms\nUpdated pytest v9.0.3 -> v9.1.1\n"
}

DEBUG: resetToCommit(c7968aee67e9c765b69ef2720bd852facaec05df) (branch="renovate/pytest")
DEBUG: Fetching branch renovate/pytest (branch="renovate/pytest")
DEBUG: Setting current branch to master (branch="renovate/pytest")
DEBUG: latest commit (branch="renovate/pytest")
{
  "branchName": "master",
  "latestCommitDate": "2026-06-30T17:48:41.000Z",
  "sha": "c7968aee67e9c765b69ef2720bd852facaec05df"
}

INFO: Branch created (branch="renovate/pytest")
{
  "commitSha": "bf24c40b069b5ac3e8c8161e67cdd761e190066d"
}

DEBUG: Ensuring PR (branch="renovate/pytest")
DEBUG: There are 0 errors and 0 warnings (branch="renovate/pytest")
DEBUG: getBranchPr(renovate/pytest) (branch="renovate/pytest")
DEBUG: findPr(renovate/pytest, undefined, open) (branch="renovate/pytest")
DEBUG: findPr(renovate/pytest, undefined, closed) (branch="renovate/pytest")
DEBUG: Found PR #171 (branch="renovate/pytest")
DEBUG: Found autoclosed PR 171 but it is too old to reopen (branch="renovate/pytest")
DEBUG: Fetching changelog: https://github.com/pytest-dev/pytest (9.0.3 -> 9.1.1) (branch="renovate/pytest")
DEBUG: Fetching changelog: https://github.com/pytest-dev/pytest (9.0.3 -> 9.1.1) (branch="renovate/pytest")
DEBUG: Not enough valid releases for dep pytest (pytest) (branch="renovate/pytest")
DEBUG: Not enough valid releases for dep pytest (pytest) (branch="renovate/pytest")
DEBUG: Creating PR (branch="renovate/pytest")
{
  "prTitle": "chore(deps): update dependency pytest to v9.1.1"
}

[github-actions[bot]]

Hi there,

This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions.

No logs at all

If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.

Finding logs on hosted app

Select me to read instructions

If you use the Mend Renovate app (GitHub):

1. Log in to the Mend Developer Portal
2. Navigate to the correct organization and repository
3. Locate the appropriate log (it may not always be the latest one)
4. Copy/paste the log contents
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

Read the Renovate docs, troubleshooting, self-hosted to learn how to find the logs.

Formatting your logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here.

Good luck,

The Renovate team

[ReenigneArcher]

I don't know what specifically you need from the logs, I tried to paste what looked relevant. I can provide other bits if needed.

Online logs are here if you have access: https://developer.mend.io/github/LizardByte/actions/-/job/019f21ea-3cfa-7a32-a36a-4f48d393d368

[RahulGautamSingh]

I will need logs from the run, the PR was autoclosed.

It will save time if you share the logs here, there's a mid summer lul at Mend so they can be slow to respond.

[ReenigneArcher]

https://gist.github.com/ReenigneArcher/78f218440e55783e0893fb870ece08aa

[RahulGautamSingh]

Thanks for the logs, that gist helped me figure out the root cause.

What's happening

Your config uses constraintsFiltering: "strict" and actions/setup_python/pyproject.toml declares requires-python = ">=3.14". In the run that closed the PR, strict filtering dropped every modern pytest release (same for requests, pygobject, python-dotenv too):

From logs:

Filtered out 129 non-matching releases out of 192 total for pytest due to constraintsFiltering=strict: ... 9.0.3, 9.1.0, 9.1.1

Note: 9.1.1 and your installed 9.0.3 are both in the filtered-out list. With no valid update left, Renovate saw renovate/pytest as a stale branch during the prune step and autoclosed PR #245 as it had no releases in this run.

Why it's wrong

pytest 9.1.1 declares requires_python = ">=3.10", and >=3.14 is a subset of >=3.10, so it should be kept.

The bug is that the python constraint is being evaluated with the pep440 versioning, which can't do range-vs-range compatibility.

The dedicated python versioning handles it correctly (python.subset(">=3.14", ">=3.10") === true), but it isn't used because the pep621 manager never registers constraintsVersioning.python = "python".

Workaround until we ship a fix:

 {
   "constraintsVersioning": {
     "python": "python"
   }
}

This routes the >=3.14 constraint through the range-aware python versioning, so 9.1.1 is kept and the PR stops getting autoclosed.

We'll track the proper fix in an issue.

[RahulGautamSingh]

Issue: #44453

[ReenigneArcher]

Thank you for the response!

Unfortunately, this seems to fail renovate config validation.

> lizardbyte-github@0.0.0 validate-renovate
> renovate-config-validator --strict ./renovate-config.json

 INFO: Validating ./renovate-config.json as global config
 INFO: Config validated successfully against 1 file(s)

> lizardbyte-github@0.0.0 validate-renovate
> renovate-config-validator --strict ./renovate-config.json5

 INFO: Validating ./renovate-config.json5 as global config
ERROR: Found errors in configuration
       "file": "./renovate-config.json5",
       "errors": [
         {
           "topic": "Configuration Error",
           "message": "Configuration option `constraintsVersioning.python` is not a valid additional constraint name, as `python` is a tool name, and `constraintsVersioning` can only override the versioning for a non-tool constraint"
         }
       ]

> lizardbyte-github@0.0.0 validate-renovate
> renovate-config-validator --strict ./renovate.json

 INFO: Validating ./renovate.json as global config
 INFO: Config validated successfully against 1 file(s)
Error: Process completed with exit code 1.

LizardByte/.github#789

[RahulGautamSingh]

Let me check. I'll update soom

[RahulGautamSingh]

My bad the constraintsVersioning.python suggestion was wrong. I overlooked that constraintsVersioning can only override versioning for non-tool constraints.

Another workaround could be to scope constraintsFiltering: "none" to the pep621 manager via packageRules.

The proper fix would be on suggested in #44453.