chore(deps): update ghcr.io/renovatebot/renovate docker tag to v42 #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/ghcr.io-renovatebot-renovate-42.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
41.173.1->42.2.0Release Notes
renovatebot/renovate (ghcr.io/renovatebot/renovate)
v42.2.0Compare Source
Features
Miscellaneous Chores
Build System
v42.1.3Compare Source
Bug Fixes
Build System
v42.1.2Compare Source
Bug Fixes
v42.1.1Compare Source
Bug Fixes
v42.1.0Compare Source
Features
uv pip compileoptions (#39167) (0b02c42)Code Refactoring
Build System
Continuous Integration
v42.0.3Compare Source
Bug Fixes
Documentation
v42.0.2Compare Source
Bug Fixes
Miscellaneous Chores
v42.0.1Compare Source
Documentation
Miscellaneous Chores
Build System
v42.0.0Compare Source
Breaking changes for 42
Using
minimumReleaseAgewill now require a release timestamp #38843When specifying
minimumReleaseAge, Renovate will look for a release timestamp to determine the age of the release, and whether it matched theminimumReleaseAgeconfiguration.Before Renovate 42, if a release timestamp was not present, Renovate would treat the dependency update as if the release timestamp was present and the dependency had passed that lifetime.
This means that users with artifact proxies, or in cases that the release timestamp wasn't consistently present could lead to dependencies "slipping through", and being updated before Renovate's policy enforced it to.
As of Renovate 42, the configuration
minimumReleaseAgeBehaviour(added in 41.150.0) requires the release timestamp to be present.If the release timestamp isn't present, Renovate will mark it as "awaiting schedule", and will output a debug log message to explain why.
You can revert to the existing behaviour by setting
minimumReleaseAgeBehaviour=timestamp-optional.Note that not all datasources support this functionality, nor do custom registries (such as Artifactory, etc).
For more details on how to verify support for your repository, check out the Minimum Release Age documentation
minimumReleaseAge: 3 dayswill now be set by default for npm inconfig:best-practices#37967For users of
config:best-practices, the Minimum Release Age functionality will now apply by default for the npm ecosystem.This will introduce a delay of 3 days between package publishing and Renovate suggesting an update for the release, so:
This will be enforced by default for packages using the
npmdatasource via thesecurity:minimumReleaseAgeNpmpreset.For more details on this functionality, check out the Minimum Release Age documentation.
Renovate now defaults to using Node.JS 24 #38939
With Node 24 now in Long Term Support (LTS) release status, we have moved to target Node.JS 24 (
^24.11.0) as our default engine for Node, and retain support for Node 22.The pre-built Docker containers have been updated to use Node 24.
If you self-host without using our Docker image, you should be able to continue running Renovate with Node 22, for instance if you build your own image, or run the
renovatenpm package.Redis clusters now authenticate to all nodes in the cluster with the provided credentials
When running Renovate against a Redis cluster with authentication, it was possible that a
NOAUTH Authentication requirederror may appear:Renovate will now use the same authentication for all nodes in a cluster.
Support Yarn Catalogs #38215
We now support the official Yarn Catalog functionality.
As part of this, we have removed support for the yarn-plugin-catalogs community plugin.
If you are using the yarn-plugin-catalogs community plugin, you will need to migrate your catalogs to the official Yarn Catalog functionality before Renovate 42 will update your dependencies.
Remove versioning modules needing to implement
rangeStrategy=pin#36261This is an internal refactor to make it easier for creating and maintaining versioning modules.
This should not be a non-breaking change, as the versioning modules will have defaults available.
However, we're releasing it as part of this major release, and highlighting it, in case it does lead to breaking changes.
PGP encryption is now performed using Bouncy Castle #39032
GPG encryption is no longer performed using
kbpgpKeybase's PGP for JavaScript), and has been replaced with a Bouncy Castle version.Some users have found license compliance issues with the
kbpgppackage, so this will now resolve them.Legacy RSA encryption has been removed #39111
Deprecated since 37.315.0 (2024-04-21), the legacy RSA encryption is now no longer available.
Change to the default User Agent #37535
The
user-agentheader for Renovate's outgoing HTTP calls has changed the default toRenovate/${version}.Default tool version updates #39100
For users of the upstream Renovate container images, the following tools have been updated to new major versions:
Commentary for 42
Focus on
minimumReleaseAgeYou'll notice that there are a number of big features here - and in recent minor releases - that focus on Minimum Release Age.
With recent supply chain attacks, the Renovate team have been hard at work improving the support we've had in Renovate (since 2019!) for this functionality, and making it as predictable as possible, so we can then enable it by default for users of
config:best-practices.You can read more about this focus in a blog post we've written on the Mend blog.
We're starting with the enabling of the
npmdatasource, but will look to extend this functionality in future major releases, based on community feedback, and ecosystem support.Deprecations
As part of this release, we want to make you aware of deprecated features which will be removed as of Renovate 43:
renovate-schema.jsonwill only support repository configuration, and a separaterenovate-admin-schema.jsonwill be needed for global/self-hosted configuration42.0.0 (2025-11-06)
⚠ BREAKING CHANGES
minimumReleaseAgefor npm (#37967)Features
minimumReleaseAgefor npm (#37967) (e371de1), closes #37952kbpgpwithbcpgp(#39032) (6de0097)Bug Fixes
Code Refactoring
Build System
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
5c0d7a64abto5bea61b7bb5bea61b7bbto941118437f941118437ftob454efa472b454efa472to3c5fc1f0db3c5fc1f0dbto26577e336726577e3367to08b4ac6db008b4ac6db0toa9675b287eView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.