-
Notifications
You must be signed in to change notification settings - Fork 1.5k
chore(deps): Update go minor and patch (main) #9494
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
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/main-go-minor-and-patch
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+152
−164
Conversation
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
4254278
to
184b88b
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
184b88b
to
28ac823
Compare
28ac823
to
395f8c3
Compare
181da97
to
e86b9a2
Compare
3e34974
to
db69bb6
Compare
1 similar comment
3c40551
to
fc46079
Compare
55357d6
to
1e52647
Compare
e24ed32
to
d0a7cfe
Compare
d0a7cfe
to
4f2c7be
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/core
internal mechanisms
area/graphql
Issues related to GraphQL support on Dgraph.
area/testing
Testing related issues
0 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.
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.
This PR contains the following updates:
v1.45.2
->v1.46.0
v1.46.1
fda084b
->8fb2c71
v2.2.0
->v2.3.0
v28.3.3+incompatible
->v28.4.0+incompatible
v1.6.0
->v1.8.0
v1.20.0
->v1.21.0
v0.37.0
->v0.39.1
v1.23.0
->v1.23.2
v1.9.2
->v1.10.0
v1.9.1
->v1.10.1
v1.0.7
->v1.0.10
v1.20.1
->v1.21.0
v1.10.0
->v1.11.1
v0.62.0
->v0.63.0
v0.62.0
->v0.63.0
v1.37.0
->v1.38.0
v1.37.0
->v1.38.0
v1.37.0
->v1.38.0
v1.37.0
->v1.38.0
v1.37.0
->v1.38.0
v0.41.0
->v0.42.0
42675ad
->df92998
v0.27.0
->v0.28.0
v0.43.0
->v0.44.0
v0.16.0
->v0.17.0
v0.35.0
->v0.36.0
v0.34.0
->v0.35.0
v0.28.0
->v0.29.0
v0.36.0
->v0.37.0
v1.74.2
->v1.75.1
v1.36.7
->v1.36.9
Release Notes
IBM/sarama (github.com/IBM/sarama)
v1.46.0
: Version 1.46.0 (2025-08-25)Compare Source
What's Changed
🎉 New Features / Improvements
🐛 Fixes
📦 Dependency updates
65e299d
by @renovate[bot] in #3164🔧 Maintenance
New Contributors
Full Changelog: IBM/sarama@v1.45.2...v1.46.0
dgraph-io/ristretto (github.com/dgraph-io/ristretto/v2)
v2.3.0
: Ristretto v2.3.0Compare Source
What's Changed
New Contributors
Full Changelog: hypermodeinc/ristretto@v2.2.0...v2.3.0
docker/docker (github.com/docker/docker)
v28.4.0+incompatible
Compare Source
graph-gophers/graphql-go (github.com/graph-gophers/graphql-go)
v1.8.0
Compare Source
What's Changed
DecodeSelectedFieldArgs
to decode argument values for any nested selected field path directly from a resolver context. Enables reflection-free multi-level prefetching / batching (e.g. Category → Products → Reviews) that only loads requested branches, mitigating N+1 query problem even with pagination & filters by @pavelnikolov in #684Full Changelog: graph-gophers/graphql-go@v1.7.2...v1.8.0
If this release helps you, please consider becoming a sponsor ❤️
v1.7.2
Compare Source
What's Changed
Full Changelog: graph-gophers/graphql-go@v1.7.1...v1.7.2
v1.7.1
Compare Source
What's Changed
SelectedFieldNames
now returns dot-delimited nested field paths (e.g.products
,products.id
,products.category
,products.category.id
). Intermediate container object/list paths are included so resolvers can check for both a branch (products.category
) and its leaves (products.category.id
).HasSelectedField
andSortedSelectedFieldNames
operate on these paths. This aligns behavior with typical resolver projection needs and fixes missing nested selections by @pavelnikolov in #680Full Changelog: graph-gophers/graphql-go@v1.7.0...v1.7.1
v1.7.0
Compare Source
What's Changed
Important
The default branch of the repository is now
main
. The previous default branch (i.e.master
) is still present but will not be updated anymore.Full Changelog: graph-gophers/graphql-go@v1.6.0...v1.7.0
mark3labs/mcp-go (github.com/mark3labs/mcp-go)
v0.39.1
Compare Source
What's Changed
outputSchema
by @alex210501 in #573Full Changelog: mark3labs/mcp-go@v0.39.0...v0.39.1
v0.39.0
Compare Source
What's Changed
New Contributors
Full Changelog: mark3labs/mcp-go@v0.38.0...v0.39.0
v0.38.0
Compare Source
What's Changed
New Contributors
Full Changelog: mark3labs/mcp-go@v0.37.0...v0.38.0
prometheus/client_golang (github.com/prometheus/client_golang)
v1.23.2
: - 2025-09-05Compare Source
This release is made to upgrade to prometheus/common v0.66.1, which drops the dependencies github.com/grafana/regexp and go.uber.org/atomic and replaces gopkg.in/yaml.v2 with go.yaml.in/yaml/v2 (a drop-in replacement). There are no functional changes.
All Changes
Full Changelog: prometheus/client_golang@v1.23.1...v1.23.2
v1.23.1
: - 2025-09-04Compare Source
This release is made to be compatible with a backwards incompatible API change in prometheus/common v0.66.0. There are no functional changes.
All Changes
Full Changelog: prometheus/client_golang@v1.23.0...v1.23.1
spf13/cast (github.com/spf13/cast)
v1.10.0
Compare Source
What's Changed
New Contributors
Full Changelog: spf13/cast@v1.9.2...v1.10.0
spf13/cobra (github.com/spf13/cobra)
v1.10.1
Compare Source
🐛 Fix
v1.0.9 of pflags brought back
ParseErrorsWhitelist
and marked it as deprecatedFull Changelog: spf13/cobra@v1.10.0...v1.10.1
v1.10.0
Compare Source
What's Changed
🚨 Attention!
This version of
pflag
carried a breaking change: it renamedParseErrorsWhitelist
toParseErrorsAllowlist
which can break builds if bothpflag
andcobra
are dependencies in your project.pflag and
cobra, upgrade
pflagto 1.0.8 and
cobrato
1.10.0`pflag
v1.0.9 which keeps the deprecatedParseErrorsWhitelist
More 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.10
Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.9...v1.0.10
v1.0.9
Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8
Compare Source
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhitelist
struct and correspondingFlagSet.parseErrorsWhitelist
field 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.0
Compare Source
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
mapstructure
package replacement. by @aldas in #2004New Contributors
Full Changelog: spf13/viper@v1.20.0...v1.21.0
stretchr/testify (github.com/stretchr/testify)
v1.11.1
Compare Source
This release fixes #1785 introduced in v1.11.0 where expected argument values implementing the stringer interface (
String() string
) with a method which mutates their value, when passed to mock.Mock.On (m.On("Method", <expected>).Return()
) or actual argument values passed to mock.Mock.Called may no longer match one another where they previously did match. The behaviour prior to v1.11.0 where the stringer is always called is restored. Future testify releases may not call the stringer method at all in this case.What's Changed
Full Changelog: stretchr/testify@v1.11.0...v1.11.1
v1.11.0
Compare Source
What's Changed
Functional Changes
v1.11.0 Includes a number of performance improvements.
Fixes
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), 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.