PR for version update is created after previous one is closed when using github-action on self-hosted runner

[WTPOptAxe]

tl;dr - What's the right way to be able to ignore specific versions when using the action instead of the app?

My understanding is that if I close a PR for a specific version update, that will not be opened again in the future - this is from reading https://docs.renovatebot.com/key-concepts/pull-requests/ - "Renovate does not need to maintain any database/state about open or closed Pull Requests."

This is not happening, and a new PR is being created for the update on the next run.

The PR titles are the same each time as you can see in the images below, and include the full new version number. This is how I understand renovate identifies a previous PR for this version.

I tried setting "recreateWhen": "never" in both my repo configuration and my self-hosted configuration files, but the behaviour persists.

If I run in debug mode, I see the following regarding lxml - it explicitly states 'Check for closed PR because recreating closed PRs is disabled.'

DEBUG: getBranchPr(renovateaction/lxml-5.x) (repository=us/us-repo-test)
DEBUG: findPr(renovateaction/lxml-5.x, undefined, open) (repository=us/us-repo-test)
DEBUG: 0 PRs are currently open (repository=us/us-repo-test)
.
.
.
DEBUG: Check for closed PR because recreating closed PRs is disabled. (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
DEBUG: findPr(renovateaction/lxml-5.x, chore(deps): update dependency lxml to v5.3.0, !open) (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
DEBUG: findPr(renovate/lxml-5.x, chore(deps): update dependency lxml to v5.3.0, !open) (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
DEBUG: prAlreadyExisted=false (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)

This doesn't seem right as I have multiple closed PRs with what I believe to be the correct name. gh cli shows the following (subset - there are more)

#56  chore(deps): update dependency lxml to v5.3.0                renovateaction/lxml-5.x  about 28 minutes ago
#55  chore(deps): update dependency lxml to v5.3.0                renovateaction/lxml-5.x  about 35 minutes ago
#54  chore(deps): update dependency lxml to v5.3.0                renovateaction/lxml-5.x  about 39 minutes ago
#53  chore(deps): update dependency lxml to v5.3.0                renovateaction/lxml-5.x  about 43 minutes ago

The PR is then created later in the log

DEBUG: Creating PR (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
       "prTitle": "chore(deps): update dependency lxml to v5.3.0"
DEBUG: Creating PR (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
       "title": "chore(deps): update dependency lxml to v5.3.0",
       "head": "us:renovateaction/lxml-5.x",
       "base": "main",
       "draft": false
DEBUG: PR created (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
       "pr": 57,
       "draft": false
DEBUG: Adding labels '' to #57 (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
 INFO: PR created (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
       "pr": 57,
       "prTitle": "chore(deps): update dependency lxml to v5.3.0"
DEBUG: addParticipants(pr=57) (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
DEBUG: setPrCache() (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)
DEBUG: Created Pull Request #57 (repository=us/us-repo-test, branch=renovateaction/lxml-5.x)

I'm using a classic PAT, not attempting to use a fine grained pat as I understand they are not supported. The PAT has Full control of private repositories enabled.

In the same repo when using the GitHub App, ignoring versions worked as expected and they were not recreated. But we need postUpgradeTasks so we're attempting to move to the action instead.

screenshots

[viceice]

you're doing something wrong with your configuration.

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[rarkins]

Most likely cause is a misconfigured "username". Renovate queries the list of PRs based on username, so if it's wrong then it won't find the previous PR

[WTPOptAxe]

Does the username need to match the owner of the PAT ?

[rarkins]

Please read the docs