feat!: v39 #32273
Merged
feat!: v39 #32273
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
viceice
requested changes
Nov 4, 2024
HonkingGoose
suggested changes
Nov 4, 2024
Updates Renovate's package.json>engines to add support for Node v22 LTS, and updates Renovate official Docker images to run on Node v22 instead of Node v20. Closes #32068 BREAKING CHANGE: Renovate Docker images will now be based on Node.js v22 instead of v20
Sets RENOVATE_BINARY_SOURCE=global in Renovate official "-full" images. Closes #32136 BREAKING CHANGE: Renovate -full images will now use binarySource=global. Set RENOVATE_BINARY_SOURCE=install to revert to dynamic tool installation.
Changes the priority order so that squash merges are preferred over rebase merge and merge commits. Doing so allows GitHub to sign the resulting commit on the base branch. BREAKING CHANGE: Renovate will now prefer squash merges over others in GitHub, if they are allowed.
…32240) Update Renovate base-image from v7 to v9. Includes the following potentially breaking changes for -full image: - Update Ubuntu base image to 24.04 - Update dependency python to v3.13.0 - Update dependency node to v22 Additionally, some changes to internal paths were made (only affects users who install things themselves or rely on static locations of binaries). BREAKING CHANGE: The Renovate full image now uses Ubuntu 24.04, Python 3.13 and Node v22
…32095) Updates default Renovate sidecar container to v13, which is based on Ubuntu 24.04. BREAKING CHANGE: Renovate sidecard images will default to use Ubuntu 24.04 instead of 20.04
…of branchName (#32278) Update logic for branchNameStrict=true so that it also removes forward slashes from branch names, with the exception of the `branchPrefix` part. In other words, if you leave the default `branchPrefix="renovate/"` then you'll get branch names like `renovate/foo-bar-42-x` instead of today's `renovate/foo/bar-42-x`. BREAKING CHANGE: Branch names with multiple forward slashes will change if branchNameStrict=true
viceice
approved these changes
Nov 4, 2024
|
🎉 This PR is included in version 39.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: