This repository was archived by the owner on Sep 11, 2025. It is now read-only.
chore(deps): Update go minor and patch #929
Merged
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.82.0->v1.83.0v28.3.0+incompatible->v28.3.1+incompatiblev1.3.2-0.20250702171307-a33bc8ea433e->v1.4.0v2.0.0-rc.194->v2.0.0-rc.198Release Notes
aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2/service/s3)
v1.83.0General Highlights
Module Highlights
github.com/aws/aws-sdk-go-v2/service/connectcases: v1.26.0github.com/aws/aws-sdk-go-v2/service/ec2: v1.229.0github.com/aws/aws-sdk-go-v2/service/s3: v1.83.0github.com/aws/aws-sdk-go-v2/service/s3control: v1.60.0docker/docker (github.com/docker/docker)
v28.3.1+incompatibleCompare Source
wundergraph/graphql-go-tools (github.com/wundergraph/graphql-go-tools/execution)
v1.4.0This release adds the "staticProxy" cmd.
Static proxy is a ready to use configurable proxy.
The proxy (currently) works with a single backend.
In the current version it comes with 2 features:
The lexer now supports an input up to 1.000.000 Byte. (Could be configured to more, would increase memory usage).
I've removed a few bottlenecks so that the proxy is able to parse 500kb schema's on a modern CPU in < 10ms. Small schemas (<50kb) can be parsed in <1ms. Query parsing and validation is usually <1ms.
This makes the library/proxy a good fit if the schema is not known ahead of time. So it's definitely possible to fetch the schema at request time, parse it and then proceed with the request.
Configuration
📅 Schedule: Branch creation - "on Wednesday" (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.