npm install renovate installs 37.440.7 instead of the latest 41.93.2

[kunzese]

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.

No response

Please tell us more about your question or problem

When installation renovate via npm install -g renovate it installs version 37.440.7 instead of the latest 41.93.2

Logs (if relevant)

Logs

$ docker run -it --rm --entrypoint bash node

$ npm install -g renovate
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated rimraf@2.4.5: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@6.0.4: Glob versions prior to v9 are no longer supported
npm warn deprecated boolean@3.2.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated openpgp@5.11.2: This version is deprecated and will no longer receive security patches. Please refer to https://github.com/openpgpjs/openpgpjs/wiki/Updating-from-previous-versions for details on how to upgrade to a newer supported version.

added 822 packages in 2m

206 packages are looking for funding
  run `npm fund` for details
npm notice
npm notice New patch version of npm available! 11.5.1 -> 11.5.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.5.2
npm notice To update run: npm install -g npm@11.5.2
npm notice

$ renovate -v
37.440.7
 
$ npm install -g renovate@latest
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'renovate@41.93.2',
npm warn EBADENGINE   required: { node: '^22.13.0', pnpm: '^10.0.0' },
npm warn EBADENGINE   current: { node: 'v24.7.0', npm: '11.5.1' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@renovatebot/kbpgp@4.0.1',
npm warn EBADENGINE   required: { node: '^20.9.0 || ^22.11.0', pnpm: '^9.0.0' },
npm warn EBADENGINE   current: { node: 'v24.7.0', npm: '11.5.1' }
npm warn EBADENGINE }
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated rimraf@2.4.5: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@6.0.4: Glob versions prior to v9 are no longer supported
npm warn deprecated boolean@3.2.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead

added 145 packages, removed 111 packages, and changed 687 packages in 14s

211 packages are looking for funding
  run `npm fund` for details

$ renovate -v
41.93.2

[github-actions[bot]]

Hi there,

You're reporting a problem with an old version of Renovate. Please try the latest version and tell us if that fixes your problem.

Be sure to provide updated logs once you have run with a newer version.

Good luck,

The Renovate team

[jamietanna]

It's unclear exactly what was going on here from the info you've provided - but trying again would be appreciated

It's worth also confirming your npm CLI version, Node version, etc for inside the container

It looks like it's likely to be related to that, and npm itself selecting a version that's supported by your tooling

[MrBasset]

Seeing a similar issue with a Azure DevOps Pipeline using a Microsoft Hosted build agent (ubuntu-latest image), even after bumping to the latest node version.

Executing:

    - task: UseNode@1
      inputs:
        version: '25.x'
    - bash: |
        echo "Running Renovate for group: ${{parameters.groupName}}"

        node --version
        npm --version

        npm install -g renovate

        renovate --version

Results in:

Running Renovate for group: group1
v25.6.1
11.9.0
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated glob@6.0.4: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated rimraf@2.4.5: Rimraf versions prior to v4 are no longer supported
npm warn deprecated boolean@3.2.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated tar@6.2.1: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated glob@10.4.5: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated @renovatebot/kbpgp@3.0.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated openpgp@5.11.2: This version is deprecated and will no longer receive security patches. Please refer to https://github.com/openpgpjs/openpgpjs/wiki/Updating-from-previous-versions for details on how to upgrade to a newer supported version.

added 799 packages in 4m

202 packages are looking for funding
  run `npm fund` for details
37.440.7

[jamietanna]

What happens with npm install -g renovate@latest or npm install -g renovate@43?

[MrBasset]

I didn't get to try, this morning as if by magic the scheduled overnight run installed the latest.

We haven't set up an NPM cache or pull-through proxy in DevOps but I can only assume that ADO automatically has something like that in play as the only thing that changed since my last manual run and last night was time since the last execution.