-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: v29 #12488
Conversation
Do we maybe want to include breaking changes for the config into this release as well? Or do we want to save those for a later release, so I'm not holding up things now? I'm talking specifically about: |
Let's wait on those. I'm not so sure about the first one either. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems valid to me from the perspective of my GOPROXY-related PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just the mentioned wording should be done. 🤗
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Last change and then I'm done. 😄
Add configuration option `detectHostRulesFromEnv`. BREAKING CHANGE: `hostRules` are no longer automatically derived from env variables such as `NPM_X_TOKEN`. Set `detectHostRulesFromEnv=true` in config to re-enable same functionality.
) Allow the usage of arbitrary capture groups inside of regex manager templates and further adds refactor which this allows. BREAKING_CHANGE Only regex managers using the combination matchStringStrategy are affected of this change! Currently capture groups which are empty but still match the regex are ignored. This is no longer the case! Subsequent matchGroups will now overwrite previous ones, even if the later one is empty.
Current implementation tries to use GOPROXY and falls back to Renovate fetching mechanism if no releases found. The new one is switches to GOPROXY implementaiton when environment variable is set and doesn't fallback. However, when direct keyword is used, it will use Renovate-native mechanism that fetches directly from GitHub, etc. When off keyword is encountered or no URLs left, we're done with no releases (i.e. no fallback to Renovate-native mechanism). BREAKING CHANGE: Go modules lookups will now no longer fallback to Renovate native lookups if GOPROXY is configured and without "direct" explicitly configured.
Flips platformAutomerge default to `false`. BREAKING CHANGE: Platform automerge is no longer enabled by default.
🎉 This PR is included in version 29.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Rollup of v29 features, to be rebase merged
Closes #12155, Closes #11944, Closes #11387