Update autoclosed unexpectedly

[nielsbasjes]

What would you like help with?

I think I found a bug

How are you running Renovate?

Mend Renovate hosted app on github.com

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

The renovate bot created a merge request and then it was almost immediately autoclosed without the update being applied. The version update this merge request holds still seems like a needed update.
nielsbasjes/prefixmap#250

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[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.

Insufficient logs

Select me to read instructions

If you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section.

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

[nielsbasjes]

I had a good look at the logging and I suspect the following happened.

• The 4.1.5 release was created https://github.com/actions/checkout/releases/tag/v4.1.5
• Then renovate ran and created the mergerequest.
• Then the 4.1.5 was reclassified as a prerelease.
• Then renovate cancelled this merge request.

So by the looks of things no error in Renovate.

[viceice]

i saw this too a couple of times recently, but didn't hat time to investigate. Thanks for sharing the details

[nielsbasjes]

And today this dependency was put back to a normal release and Renovate correctly reopened the merge request.