Renovate detected new version of Node 22 image but the PR was not created

[rvillane]

How are you running Renovate?

Self-hosted Renovate

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

GitHub Enterprise Cloud (github.com)

Please tell us more about your question or problem

I have a GHE repo with a Dockerfile like the following:

FROM node:22.10.0-bookworm@sha256:da53547a061beb7f11f58ee2231589b999acfca89bdf6dfd740627340c879f63

WORKDIR /tmp

RUN apt-get update && \
    apt-get upgrade -y && \
    apt-get --yes install --no-install-recommends yamllint jq zip && \
    npm install -g semver && \
    rm -rf /usr/local/lib/node_modules/npm/node_modules/node-gyp/test/fixtures/server.key

USER node

and the GHE repo has this renovate.json file to avoid renovate to suggest updates for Node versions other and v22

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:base", ":disableDependencyDashboard"],
  "packageRules": [
    {
      "matchPackageNames": ["node"],
      "allowedVersions": "22"
    }    
  ]
}

Renovate bot ran successfully and detected version 22.11.0 is available:

DEBUG: packageFiles with updates (repository=MyOrg/nodejs-v22-image, baseBranch=main)
       "config": {
         "dockerfile": [
           {
             "deps": [
               {
                 "depName": "node",
                 "currentValue": "22.10.0-bookworm",
                 "currentDigest": "sha256:da53547a061beb7f11f58ee2231589b999acfca89bdf6dfd740627340c879f63",
                 "replaceString": "node:22.10.0-bookworm@sha256:da53547a061beb7f11f58ee2231589b999acfca89bdf6dfd740627340c879f63",
                 "autoReplaceStringTemplate": "{{depName}}{{#if newValue}}:{{newValue}}{{/if}}{{#if newDigest}}@{{newDigest}}{{/if}}",
                 "datasource": "docker",
                 "depType": "final",
                 "updates": [
                   {
                     "bucket": "non-major",
                     "newVersion": "22.11.0",
                     "newValue": "22.11.0-bookworm",
                     "newDigest": "sha256:5c76d05034644fa8ecc9c2aa84e0a83cd981d0ef13af5455b87b9adf5b216561",
                     "releaseTimestamp": "2024-11-13T22:41:37.448Z",
                     "newVersionAgeInDays": 6,
                     "newMajor": 22,
                     "newMinor": 11,
                     "newPatch": 0,
                     "updateType": "minor",
                     "pendingChecks": true,
                     "branchName": "renovate/all-minor-patch"
                   }
                 ],
                 "packageName": "node",
                 "versioning": "node",
                 "warnings": [],
                 "sourceUrl": "https://github.com/nodejs/node",
                 "registryUrl": "https://index.docker.io",
                 "lookupName": "library/node",
                 "currentVersion": "22.10.0",
                 "currentVersionTimestamp": "2024-10-19T18:42:09.623Z",
                 "currentVersionAgeInDays": 31,
                 "isSingleVersion": true,
                 "fixedVersion": "22.10.0"
               }
             ],
             "packageFile": "Dockerfile"
           }
         ]
       }
```

but the actual PR was never created and no error was produced:
```
DEBUG: Repo is activated (repository=MyOrg/nodejs-v22-image)
DEBUG: Branch summary (repository=MyOrg/nodejs-v22-image)
       "cacheModified": undefined,
       "baseBranches": [{"branchName": "main", "sha": "dfdd41017e6ad83930cf1afcc5510370dcaf2797"}],
       "branches": [],
       "defaultBranch": "main",
       "inactiveBranches": ["renovate/all-minor-patch"]
DEBUG: branches info extended (repository=MyOrg/nodejs-v22-image)
       "branchesInformation": [
         {
           "branchName": "renovate/all-minor-patch",
           "prNo": null,
           "prTitle": "Update Node.js to v22.11.0",
           "result": "pending",
           "upgrades": [
             {
               "datasource": "docker",
               "depName": "node",
               "displayPending": "",
               "fixedVersion": "22.10.0",
               "currentVersion": "22.10.0",
               "currentValue": "22.10.0-bookworm",
               "currentDigest": "sha256:da53547a061beb7f11f58ee2231589b999acfca89bdf6dfd740627340c879f63",
               "newValue": "22.11.0-bookworm",
               "newVersion": "22.11.0",
               "newDigest": "sha256:5c76d05034644fa8ecc9c2aa84e0a83cd981d0ef13af5455b87b9adf5b216561",
               "packageFile": "Dockerfile",
               "updateType": "minor",
               "packageName": "node"
             }
           ]
         }
       ]
```

I'm scratching my head why no PR was created in this case

thanks

link to the full debug log is available here -> https://gist.github.com/rvillane/704560d24d4b973bddb68ba5e6d5b843

### Logs (if relevant)

<details><summary>Logs</summary>
https://gist.github.com/rvillane/704560d24d4b973bddb68ba5e6d5b843
</details>

[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

[rvillane]

that message about missing logs is not fully clear to me as logs were provided

[RahulGautamSingh]

Maybe it was missed, as we normally expect you to put them in the Logs section. You can edit the description to add the link in Logs section

[RahulGautamSingh]

The reason must be minimumReleaseAge.

You extend the config:base preset which default to using minimumReleaseAge-7days and currently the release in only "6 days" old (newReleaseAgeInDays=6 in logs), hence no PR was created.

Also in the logs you can see pendingChecks=true which means some checks did not pass, which will affect the PR creation.

[rarkins]

There's not enough logs

[rvillane]

The reason must be minimumReleaseAge.

You extend the config:base preset which default to using minimumReleaseAge-7days and currently the release in only "6 days" old (newReleaseAgeInDays=6 in logs), hence no PR was created.

Also in the logs you can see pendingChecks=true which means some checks did not pass, which will affect the PR creation.

Thanks @RahulGautamSingh, you were right, changed minimumReleaseAge from 7 to 5 and now the bot created the PR as expected. I think there is an opportunity here to improve logging and make more explicit the reasons why a PR was not created.

thanks a lot for your help