Repository navigation
fix(deps): update all major (major) - #410
Open
renovate[bot] wants to merge 2 commits into
Open
renovate[bot] wants to merge 2 commits into
renovate[bot] wants to merge 2 commits into
Conversation
renovate
Bot
force-pushed
the
renovate/major-all-major
branch
7 times, most recently
from
September 17, 2026 16:41
ba867b8 to
42510fa
Compare
renovate
Bot
force-pushed
the
renovate/major-all-major
branch
from
September 18, 2026 09:42
42510fa to
59b693f
Compare
renovate
Bot
force-pushed
the
renovate/major-all-major
branch
3 times, most recently
from
September 25, 2026 21:02
e643c71 to
499f64c
Compare
renovate
Bot
force-pushed
the
renovate/major-all-major
branch
2 times, most recently
from
September 30, 2026 12:43
e078731 to
f64afe0
Compare
renovate
Bot
force-pushed
the
renovate/major-all-major
branch
from
September 30, 2026 15:29
f64afe0 to
7baf4ef
Compare
client-go v3 changed DefaultBranchProtectionDefaultsOptions.AllowedToMerge and AllowedToPush from *[]*GroupAccessLevel to []*GroupAccessLevel. Drop the extra indirection at both call sites and in their tests. The settings converter generator emits the gitlab import from a backtick template, which renovate's gomodUpdateImportPaths cannot rewrite. Regenerating therefore reintroduced client-go/v2, pulled it back into go.mod via go mod tidy and broke check-diff. Point the template at v3. Renovate's import rewrite also ran gofmt over generated_settings_converters.go, which silently fixed three pre-existing mis-indentations the generator produces: the DefaultBranchProtectionDefaults, RestrictedVisibilityLevels and ElasticsearchURL snippets each carry a leading tab while the template already adds one. Drop those tabs so the generator output matches the committed file again. free-disk-space v2 renamed the tool-cache input to preinstalled-runtimes. The old name still works until v3 but emits a deprecation warning. Its other two breaking changes do not apply here: swap-storage is set explicitly, and the new "specific option overrides general" policy leaves dotnet removal unchanged. golangci-lint still reports 55 govet findings for gitlab.Ptr, which client-go v3 deprecates in favour of new(). That migration needs Go 1.26+ language semantics and follows in a separate change. Signed-off-by: Markus Siebert <markus.siebert@deutschebahn.com> Assisted-by: Kiro:claude-opus-5
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This file contains hidden or 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
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.
This PR contains the following updates:
v2.64.0→v3.15.0v1.3.2→v2.0.0Release Notes
gitlab-org/api/client-go (gitlab.com/gitlab-org/api/client-go/v2)
v3.15.0Compare Source
3.15.0
🚀 Features
3.15.0 (2026-09-28)
Features
v3.14.0Compare Source
3.14.0
🚀 Features
3.14.0 (2026-09-24)
Features
v3.13.1Compare Source
Features
3.13.1
🐛 Bug Fixes
3.13.1 (2026-09-24)
Bug Fixes
3.13.0
🚀 Features
v3.13.0Compare Source
3.13.0
🚀 Features
3.13.0 (2026-09-21)
Features
v3.12.0Compare Source
3.12.0
🚀 Features
🔄 Other Changes
3.12.0 (2026-09-17)
Features
v3.11.0Compare Source
3.11.0
🚀 Features
🔄 Other Changes
3.11.0 (2026-09-16)
Features
v3.10.0Compare Source
3.10.0
🚀 Features
3.10.0 (2026-09-14)
Features
v3.9.0Compare Source
3.9.0
🚀 Features
3.9.0 (2026-09-13)
Features
v3.8.0Compare Source
3.8.0
🚀 Features
3.8.0 (2026-09-12)
Features
v3.7.0Compare Source
3.7.0
🚀 Features
3.7.0 (2026-09-12)
Features
v3.6.0Compare Source
3.6.0
🚀 Features
3.6.0 (2026-09-11)
Features
v3.5.0Compare Source
3.5.0
🚀 Features
🔄 Other Changes
3.5.0 (2026-09-11)
Features
v3.4.0Compare Source
3.4.0
🚀 Features
3.4.0 (2026-09-10)
Features
v3.3.0Compare Source
3.3.0
🚀 Features
3.3.0 (2026-09-10)
Features
v3.2.0Compare Source
3.2.0
🚀 Features
🐛 Bug Fixes
3.2.0 (2026-09-09)
Bug Fixes
Features
v3.1.0Compare Source
3.1.0
🚀 Features
🔄 Other Changes
Ptrinternal to the library, leave the Ptr function until 4.0 (!3030) by Patrick Rice3.1.0 (2026-09-09)
Features
v3.0.0Compare Source
3.0.0
💥 Breaking Changes
3.0.0 (2026-09-07)
Bug Fixes
Features
re_requestedandstateon merge request webhook reviewers (8ef279d)BREAKING CHANGES
jlumbroso/free-disk-space (jlumbroso/free-disk-space)
v2.0.0: — three breaking changes, each with its reasonCompare Source
Breaking changes
swap-storagenow defaults tofalse. Closes #12 — reported and diagnosed by @zaikunzhang, whose proposed documentation fallback became the new FAQ. Removing swap can kill a job under memory pressure with no error pointing back at the cleanup step; a default should not break something that elementary.tool-cacheis renamedpreinstalled-runtimes. The old name still works until v3.0.0 and prints a deprecation warning. (Its default is unchanged:false, as it has been since 2022.) The new name says what actually breaks when you enable it: the runtimes thatactions/setup-node,setup-python,setup-go, andsetup-rubyrely on.dotnet: falseexempts .NET from every removal path, includinglarge-packages. Fixes #33 — reported by @ashleney; the overlap was first reported by @gmij in #6, and @ax3l explained the overlapping removal paths and a workaround. The policy is explicit, and this release applies it to .NET; future subject options add and test their own exemptions.Upgrading from v1 to v2
Most workflows need no change.
tool-cache:, rename it topreinstalled-runtimes:. The old name still works until v3.0.0 and prints a warning.swap-storage: true. It now defaults tofalse, because removing swap can kill a job under memory pressure with no error pointing back here (#12).dotnet: falseand were surprised that .NET was still removed, that is fixed — a specific option now overrides a general one (#33).Also in this release
A README FAQ ("what are the possible side-effects of these settings?"),
CONTRIBUTING.md, and a workflow example for running cleanup conditionally (#22). The reasons behind every design decision live indocs/adr/— including ADR-0007, the record of this release's default change, written the day it was decided.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.