Repository navigation
Conversation
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/non-major-dependency-updates
branch
from
August 19, 2025 20:07
3d537d9 to
eac8d81
Compare
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/non-major-dependency-updates
branch
from
August 21, 2025 00:33
eac8d81 to
a674c60
Compare
renovate-bot
force-pushed
the
renovate/non-major-dependency-updates
branch
5 times, most recently
from
September 7, 2025 14:08
91e4dcd to
4bea8db
Compare
renovate-bot
force-pushed
the
renovate/non-major-dependency-updates
branch
3 times, most recently
from
September 8, 2025 22:52
ebbef49 to
8cbfd3e
Compare
renovate-bot
force-pushed
the
renovate/non-major-dependency-updates
branch
from
September 9, 2025 19:02
8cbfd3e to
ee09785
Compare
nancynh
approved these changes
Sep 9, 2025
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
3 participants
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:
v1.15.5->v1.15.6v22.5.0->v22.6.0v5.7.5->v5.7.6v1.9.1->v1.10.1v1.0.7->v1.0.10v1.20.1->v1.21.0v0.30.0->v0.31.0v0.35.0->v0.36.0v0.246.0->v0.249.0Release Notes
googlecloudplatform/alloydb-go-connector (cloud.google.com/go/alloydbconn)
v1.15.6Compare Source
Bug Fixes
coreos/go-systemd (github.com/coreos/go-systemd/v22)
v22.6.0Compare Source
This release bumps Go requirement to 1.23, modernizes code, improves CI
and documentation, fixes a few bugs, and adds a new dbus method.
What's Changed
New Contributors
Full Changelog: coreos/go-systemd@v22.5.0...v22.6.0
jackc/pgx (github.com/jackc/pgx/v5)
v5.7.6Compare Source
spf13/cobra (github.com/spf13/cobra)
v1.10.1Compare Source
🐛 Fix
v1.0.9 of pflags brought back
ParseErrorsWhitelistand marked it as deprecatedFull Changelog: spf13/cobra@v1.10.0...v1.10.1
v1.10.0Compare Source
What's Changed
🚨 Attention!
This version of
pflagcarried a breaking change: it renamedParseErrorsWhitelisttoParseErrorsAllowlistwhich can break builds if bothpflagandcobraare dependencies in your project.pflag andcobra, upgradepflagto 1.0.8 andcobrato1.10.0`pflagv1.0.9 which keeps the deprecatedParseErrorsWhitelistMore details can be found here: #2303 (comment)
✨ Features
🐛 Fix
🪠 Testing
📝 Docs
New Contributors
Full Changelog: spf13/cobra@v1.9.1...v1.9.2
spf13/pflag (github.com/spf13/pflag)
v1.0.10Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.9...v1.0.10
v1.0.9Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8Compare Source
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhiteliststruct and correspondingFlagSet.parseErrorsWhitelistfield have been renamed toParseErrorsAllowlist.This should result in compilation errors in any code that uses these fields, which can be fixed by adjusting the names at call sites. There is no change in semantics or behavior of the struct or field referred to by these names. If your code compiles without errors after bumping to/past v1.0.8, you are not affected by this change.
The breaking change was reverted in v1.0.9, by means of re-introducing the old names with deprecation warnings. The plan is still to remove them in a future release, so if your code does depend on the old names, please change them to use the new names at your earliest convenience.
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.7...v1.0.8
spf13/viper (github.com/spf13/viper)
v1.21.0Compare Source
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
mapstructurepackage replacement. by @aldas in #2004New Contributors
Full Changelog: spf13/viper@v1.20.0...v1.21.0
googleapis/google-api-go-client (google.golang.org/api)
v0.249.0Compare Source
Features
v0.248.0Compare Source
Features
v0.247.0Compare Source
Features
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.
👻 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.