-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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(platform/bitbucket): use development branching model as default branch #20803
feat(platform/bitbucket): use development branching model as default branch #20803
Conversation
…ebot#19942) Changes `rangeStrategy` default value from `'replace'` to `'auto'`. Changes `auto` behavior so that `update-lockfile` is preferred if the manager supports the `updateLockedDependency()` function. Closes renovatebot#19800 BREAKING CHANGE: Renovate will now default to updating locked dependency versions. To revert to previous behavior, configure rangeStrategy=replace.
…novatebot#19958) Sets new defaults: - `prConcurrentLimit`: 10 (instead of 0) - `prHourlyLimit`: 2 (instead of 0) Closes renovatebot#19800 BREAKING CHANGE: Renovate now defaults to applying hourly and concurrent PR limits. To revert to unlimited, configure them back to `0`.
Set default GOPROXY value to match `go`'s own default. Closes renovatebot#20040 BREAKING CHANGE: Renovate will now use go's default `GOPROXY` settings. To avoid using the public proxy, configure `GOPROXY=direct`.
Checks file cache for expired items at the end of a run. Non-breaking change but it may result in some long cleanup jobs for any bots which have been left to populate their package cache for a long time. Closes renovatebot#13732
…ebot#20150) Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
…git tag, and preserve existing digest semantics as separate datasource (renovatebot#20178) Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com> Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: Michael Kriese <michael.kriese@visualon.de> Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Removes "includeForks" option and replaces with "forkProcessing". New default behavior is to process forks if automerge=false. Closes renovatebot#20752 BREAKING CHANGE: Forked repos will now be processed automatically if autodiscover=false. includeForks is removed and replaced by new option forkProcessing.
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.
Please mark as breaking and target v35 branch
Sure - can do. Will add a few more test cases also |
…ebot#19942) Changes `rangeStrategy` default value from `'replace'` to `'auto'`. Changes `auto` behavior so that `update-lockfile` is preferred if the manager supports the `updateLockedDependency()` function. Closes renovatebot#19800 BREAKING CHANGE: Renovate will now default to updating locked dependency versions. To revert to previous behavior, configure rangeStrategy=replace.
…novatebot#19958) Sets new defaults: - `prConcurrentLimit`: 10 (instead of 0) - `prHourlyLimit`: 2 (instead of 0) Closes renovatebot#19800 BREAKING CHANGE: Renovate now defaults to applying hourly and concurrent PR limits. To revert to unlimited, configure them back to `0`.
Co-authored-by: Rhys Arkins <rhys@arkins.net>
Co-authored-by: Rhys Arkins <rhys@arkins.net>
I see #20800 and #20811 as being related to this change, but not blocking this change. I'd like to propose this feature request moves forward as it has benefits for any new PRs and there are a few manual workarounds teams can use (or currently use) to correct existing PRs, such as
|
was able to make this a non-breaking change by adding the @rarkins - with this in place, is it still OK to target this PR to |
you can target main when it's not breaking. do you plan to support more branching models? so this config option should be a enum with null being disabled / current behavior ? |
Can you please explain a bit more about what you mean by "more branching models"? Development branch is Atlassian Bitbucket terminology and can be configured to any branch. Examples below on how this could be configured by each repository admin |
181a4d7
to
a4ab452
Compare
Sorry this was closed unintentionally by GitHub when v35 was closed |
All good. Will re-open a new PR to continue the discussion |
Changes
Updates the Bitbucket Cloud repository initialization logic to fetch and set the development branch name instead of relying only on the main branch name.
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: