Skip to content

Update all non-major dependencies (main) #709

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
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate-rancher[bot]
Copy link
Contributor

@renovate-rancher renovate-rancher bot commented Mar 13, 2025

This PR contains the following updates:

Package Type Update Change
github.com/minio/minio-go/v7 require patch v7.0.87 -> v7.0.94
github.com/onsi/ginkgo/v2 require minor v2.22.2 -> v2.23.4
github.com/onsi/gomega require minor v1.36.2 -> v1.37.0
github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring require minor v0.80.1 -> v0.83.0
github.com/samber/lo require minor v1.49.1 -> v1.51.0
github.com/testcontainers/testcontainers-go require minor v0.35.0 -> v0.37.0
golang.org/x/crypto replace minor v0.35.0 -> v0.39.0
golang.org/x/sync require minor v0.12.0 -> v0.15.0
google.golang.org/grpc replace minor v1.71.0 -> v1.73.0

Release Notes

minio/minio-go (github.com/minio/minio-go/v7)

v7.0.94

Compare Source

v7.0.93: Bugfix Release

Compare Source

What's Changed

New Contributors

Full Changelog: minio/minio-go@v7.0.92...v7.0.93

v7.0.92: Bugfix Release and new APIs

Compare Source

What's Changed

New Contributors

Full Changelog: minio/minio-go@v7.0.91...v7.0.92

v7.0.91: Bugfix Release

Compare Source

What's Changed

New Contributors

Full Changelog: minio/minio-go@v7.0.90...v7.0.91

v7.0.90: Bugfix v7.0.90

Compare Source

What's Changed

New Contributors

Full Changelog: minio/minio-go@v7.0.89...v7.0.90

v7.0.89: Bugfix Release

Compare Source

What's Changed

New Contributors

Full Changelog: minio/minio-go@v7.0.88...v7.0.89

v7.0.88: Bugfix Release

Compare Source

What's Changed

New Contributors

Full Changelog: minio/minio-go@v7.0.87...v7.0.88

onsi/ginkgo (github.com/onsi/ginkgo/v2)

v2.23.4

Compare Source

2.23.4

Prior to this release Ginkgo would compute the incorrect number of available CPUs when running with -p in a linux container. Thanks to @​emirot for the fix!

Features
  • Add automaxprocs for using CPUQuota [2b9c428]
Fixes
  • clarify gotchas about -vet flag [1f59d07]
Maintenance

v2.23.3

Compare Source

2.23.3

Fixes
  • allow - as a standalone argument [cfcc1a5]
  • Bug Fix: Add GinkoTBWrapper.Chdir() and GinkoTBWrapper.Context() [feaf292]
  • ignore exit code for symbol test on linux [88e2282]

v2.23.2

Compare Source

2.23.2

🎉🎉🎉

At long last, some long-standing performance gaps between ginkgo and go test have been resolved!

Ginkgo operates by running go test -c to generate test binaries, and then running those binaries. It turns out that the compilation step of go test -c is slower than go test's compilation step because go test strips out debug symbols (ldflags=-w) whereas go test -c does not.

Ginkgo now passes the appropriate ldflags to go test -c when running specs to strip out symbols. This is only done when it is safe to do so and symbols are preferred when profiling is enabled and when ginkgo build is called explicitly.

This, coupled, with the instructions for disabling XProtect on MacOS yields a much better performance experience with Ginkgo.

v2.23.1

Compare Source

2.23.1

🚨 For users on MacOS 🚨

A long-standing Ginkgo performance issue on MacOS seems to be due to mac's antimalware XProtect. You can follow the instructions here to disable it in your terminal. Doing so sped up Ginkgo's own test suite from 1m8s to 47s.

Fixes

Ginkgo's CLI is now a bit clearer if you pass flags in incorrectly:

  • make it clearer that you need to pass a filename to the various profile flags, not an absolute directory [a0e52ff]
  • emit an error and exit if the ginkgo invocation includes flags after positional arguments [b799d8d]

This might cause existing CI builds to fail. If so then it's likely that your CI build was misconfigured and should be corrected. Open an issue if you need help.

v2.23.0

Compare Source

2.23.0

Ginkgo 2.23.0 adds a handful of methods to GinkgoT() to make it compatible with the testing.TB interface in Go 1.24. GinkgoT().Context(), in particular, is a useful shorthand for generating a new context that will clean itself up in a DeferCleanup(). This has subtle behavior differences from the golang implementation but should make sense in a Ginkgo... um... context.

Features
  • bump to go 1.24.0 - support new testing.TB methods and add a test to cover testing.TB regressions [37a511b]
Fixes
  • fix edge case where build -o is pointing at an explicit file, not a directory [7556a86]
  • Fix binary paths when precompiling multiple suites. [4df06c6]
Maintenance
onsi/gomega (github.com/onsi/gomega)

v1.37.0

Compare Source

1.37.0

Features
  • add To/ToNot/NotTo aliases for AsyncAssertion [5666f98]

v1.36.3

Compare Source

1.36.3

Maintenance
prometheus-operator/prometheus-operator (github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring)

v0.83.0: 0.83.0 / 2025-05-30

Compare Source

  • [FEATURE] Add limits option for Alertmanager silences. #​7478
  • [FEATURE] Add NoTranslation as a translationStrategy option to OTLP config. #​7539
  • [FEATURE] Add nameEscapingScheme field to Prometheus CRDs. #​7538
  • [FEATURE] Add convertHistogramsToNHCB field to OTLPConfig. #​7533
  • [FEATURE] Add convert_classic_histograms_to_nhcb option to Prometheus global config. #​7543
  • [FEATURE] Add new MetricNameEscapingScheme and MetricNameValidationScheme parameters to ScrapeConfig. #​7555
  • [ENHANCEMENT] Do not insert sharding relabeling in scrapeConfigs if already present. #​7421

v0.82.2: 0.82.2 / 2025-05-12

Compare Source

  • [BUGFIX] Fix Alertmanager peer discovery for Alertmanager when using custom service name. #​7512
  • [BUGFIX] Fix parsing role field in openstackSDConfigs in ScrapeConfig CRD. #​7516

v0.82.1: 0.82.1 / 2025-05-06

Compare Source

  • [BUGFIX] Fix ThanosRuler when no remote-write configuration is defined. #​7498

v0.82.0: 0.82.0 / 2025-04-17

Compare Source

  • [CHANGE] Add more API validations to the ScrapeConfig CRD. #​7413
  • [CHANGE] Remove web console arguments if Prometheus version >= 3. #​7457
  • [FEATURE] Add RemoteWrite support for ThanosRuler CRD. Note that when remote write is configured, Thanos Ruler runs in stateless mode. #​7444
  • [FEATURE] Add msTeamsV2Configs receiver to AlertManagerConfig CRD. #​7464
  • [FEATURE] Add content, username and avatarURL fields to discordConfigs receiver in AlertmanagerConfig CRD. #​7307
  • [FEATURE] Add convertClassicHistogramsToNHCB field to ServiceMonitor, PodMonitor, Probe and ScrapeConfig CRDs. #​7448
  • [FEATURE] Add timeout field to webhookConfigs receiver in AlertManagerConfig CRD. #​7310
  • [FEATURE] Add additionalArgs field to AlertManager CRD. #​7385
  • [ENHANCEMENT] Add maxSamplesPerSend field to RemoteWrite Metadata Config. #​7443
  • [ENHANCEMENT] Add the terminationGracePeriodSeconds to the Alertmanager, Prometheus, PrometheusAgent and ThanosRuler CRDs. #​7439
  • [ENHANCEMENT] Validate proxyURL field in AlertManagerConfig CRD. #​6876
  • [BUGFIX] Fix nameValidationScheme support for Prometheus and PrometheusAgent CRDs. #​7414
  • [BUGFIX] Support socks5 scheme in proxyUrl field for all CRDs. #​7460 #​7466

v0.81.0: 0.81.0 / 2025-03-11

Compare Source

  • [CHANGE] Remove the lower-case hypervisor and instance roles for the OpenStack Service Discovery from the ScrapeConfig CRD (users are required to use Hypervisor and Instance instead). #​7370
  • [FEATURE] Add serviceName field to the ThanosRuler and Alertmanager CRDs. #​7325
  • [FEATURE] Add shardRetentionPolicy field to the Prometheus CRD (it requires the PrometheusShardRetentionPolicy feature gate). #​7274
  • [FEATURE] Add support for the cluster mTLS configuration to the Alertmanager CRD. #​7149
  • [FEATURE] Add LoadBalancer role for the OpenStack Service Discovery to the ScrapeConfig CRD. #​7356
  • [ENHANCEMENT] Add enableServiceLinks field to the Alertmanager, Prometheus, PrometheusAgent and ThanosRuler CRDs. #​7384
  • [BUGFIX] Fix Alertmanager configuration with PushOver duration fields. #​7249
samber/lo (github.com/samber/lo)

v1.51.0

Compare Source

What's Changed

Doc

Dependencies

New Contributors

Full Changelog: samber/lo@v1.50.0...v1.51.0

v1.50.0

Compare Source

What's Changed

Here is the 50th minor version !! 🔥🥂

New methods
Improvements
Documentation
Dependencies

New Contributors

Full Changelog: samber/lo@v1.49.1...v1.50.0

testcontainers/testcontainers-go (github.com/testcontainers/testcontainers-go)

v0.37.0

Compare Source

What's Changed

🔒 Security

  • chore(deps): bump golang.org/x/crypto from 0.31.0 to 0.35.0 in /modules/aerospike (#​3105) @​dependabot[bot]
  • chore(pulsar): bump github.com/apache/pulsar-client-go from 0.10.0 to 0.14.0 in /modules/pulsar (#​3100) @​mdelapenya
  • chore(clickhouse): bump github.com/ClickHouse/clickhouse-go/v2 from 2.20.0 to 2.34.0 in /modules/clickhouse (#​3099) @​dependabot[bot]
  • security(compose): upgrade github.com/docker/compose/v2 to fix security vulnerability (#​3095) @​sigi-glovebox

🚀 Features

🐛 Bug Fixes

📖 Documentation

🧹 Housekeeping

📦 Dependency updates

v0.36.0

Compare Source

What's Changed

⚠️ Breaking Changes

  • feat(azure)!: add Azurite, EventHubs and ServiceBus in the new Azure module, deprecating the old Azurite module (#​3008) @​mdelapenya

Users of the old Azurite module must update their code to use the new Azure module instead, which contains the same functionality under the azurite sub-package.
We took this opportunity to remove the unnecessarily exported Settings field from the Azurite container type,
so users of the Azurite container type must update their code to simply do not use that field.

  • chore(deps)!: bump github.com/docker/docker from 27.1.1+incompatible to 28.0.1+incompatible (#​3017) @​dependabot[bot]

Bumping the Docker package to a newer major version came with lots of benefits, but also some breaking changes. For that reason, users of the following
container methods and types must update their code to use the new types and methods instead:

  • Container.Inspect: the return type has been changed from types.ContainerJSON to container.InspectResponse.
  • Container.State: the return type has been changed from types.ContainerState to container.State.
  • DockerProvider.ContainerFromType: the method signature has been changed to accept a container.Summary instead of a types.Container.
    At the same time, if consuming Docker types or methods, users must update their code to use the new types and methods instead.
    As a good rule of thumb, users of the "github.com/docker/docker/api/types" package must update their code to use "github.com/docker/docker/api/types/container" instead.

Users of the deprecated DockerCompose type from the compose module must update their code to use DockerComposer instead.
The former unexported dockerCompose type has been renamed to DockerCompose. This breaking change was done because returning
an un-exported type from a constructor function limits the flexibility and usability of the returned instance. Callers could use
the exported methods, but could not declare variables of that type, pass instances to other functions, or embed them in structs
without exposing the constructor itself. This breaking change was needed to improve the usability of the compose module.

Users of the testcontainers.Logging variable and the testcontainers.TestLogger function must update their code to use the new log.Default() logger instance and the log.TestLogger() function instead, and
users of the testcontainers.Logger interface must update their code to use the new log.Logger interface instead.
The new log package allows users to set a custom logger instance calling the log.SetDefault(l log.Logger) function.
This breaking change was needed to improve the usability of the logging functionality when using the testcontainers package.

Users of the NATS module and the ConnectionString type must remove the variadic arguments from the ConnectionString method. This breaking change was needed because those arguments weren't in use.

We fixed a typo in the exported field of the ContainerRequest struct, so users of the EnpointSettingsModifier type must update their code to use the EndpointSettingsModifier type instead.

🔒 Security

🚀 Features

🐛 Bug Fixes

📖 Documentation

🧹 Housekeeping


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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@renovate-rancher renovate-rancher bot requested a review from a team as a code owner March 13, 2025 18:12
@renovate-rancher renovate-rancher bot added the dependencies Pull requests that update a dependency file label Mar 13, 2025
@renovate-rancher renovate-rancher bot force-pushed the renovate/main-all-minor-patch branch from 35ad04e to 3516a91 Compare March 18, 2025 23:52
Copy link
Contributor Author

renovate-rancher bot commented Mar 18, 2025

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 22 additional dependencies were updated

Details:

Package Change
google.golang.org/genproto/googleapis/rpc v0.0.0-20250115164207-1a7da9e5054f -> v0.0.0-20250324211829-b45e905df463
github.com/klauspost/cpuid/v2 v2.2.9 -> v2.2.10
go.opentelemetry.io/otel v1.34.0 -> v1.35.0
go.opentelemetry.io/otel/metric v1.34.0 -> v1.35.0
go.opentelemetry.io/otel/sdk v1.34.0 -> v1.35.0
go.opentelemetry.io/otel/trace v1.34.0 -> v1.35.0
golang.org/x/mod v0.23.0 -> v0.25.0
golang.org/x/net v0.38.0 -> v0.40.0
golang.org/x/oauth2 v0.27.0 -> v0.28.0
golang.org/x/sys v0.31.0 -> v0.33.0
golang.org/x/term v0.30.0 -> v0.32.0
golang.org/x/text v0.23.0 -> v0.26.0
golang.org/x/tools v0.30.0 -> v0.33.0
google.golang.org/genproto/googleapis/api v0.0.0-20250106144421-5f5ef82da422 -> v0.0.0-20250324211829-b45e905df463
google.golang.org/protobuf v1.36.5 -> v1.36.6
cel.dev/expr v0.19.1 -> v0.23.0
dario.cat/mergo v1.0.0 -> v1.0.1
github.com/docker/docker v27.1.1+incompatible -> v28.0.1+incompatible
github.com/google/pprof v0.0.0-20241210010833-40e02aabc2ad -> v0.0.0-20250403155104-27863c87afa6
github.com/magiconair/properties v1.8.7 -> v1.8.10
github.com/opencontainers/image-spec v1.1.0 -> v1.1.1
github.com/yusufpapurcu/wmi v1.2.3 -> v1.2.4
File name: tests/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 19 additional dependencies were updated

Details:

Package Change
github.com/fxamacker/cbor/v2 v2.7.0 -> v2.8.0
github.com/google/btree v1.0.1 -> v1.1.3
github.com/gorilla/websocket v1.5.3 -> v1.5.4-0.20250319132907-e064f32e3674
github.com/klauspost/compress v1.17.11 -> v1.18.0
github.com/prometheus/client_golang v1.20.5 -> v1.22.0
github.com/prometheus/common v0.61.0 -> v0.62.0
golang.org/x/crypto v0.36.0 -> v0.38.0
golang.org/x/net v0.38.0 -> v0.40.0
golang.org/x/oauth2 v0.25.0 -> v0.27.0
golang.org/x/sync v0.12.0 -> v0.14.0
golang.org/x/sys v0.31.0 -> v0.33.0
golang.org/x/term v0.30.0 -> v0.32.0
golang.org/x/text v0.23.0 -> v0.25.0
k8s.io/apiextensions-apiserver v0.32.1 -> v0.33.1
k8s.io/apiserver v0.32.1 -> v0.33.1
k8s.io/client-go v0.32.1 -> v0.33.1
k8s.io/component-base v0.32.1 -> v0.33.1
k8s.io/utils v0.0.0-20241210054802-24370beab758 -> v0.0.0-20250502105355-0f33e8f1c979
sigs.k8s.io/structured-merge-diff/v4 v4.6.0 -> v4.7.0

@renovate-rancher renovate-rancher bot force-pushed the renovate/main-all-minor-patch branch 4 times, most recently from a25e494 to e0029a5 Compare March 22, 2025 04:37
@renovate-rancher renovate-rancher bot force-pushed the renovate/main-all-minor-patch branch 3 times, most recently from 06c39d9 to b76c4af Compare April 3, 2025 04:38
@renovate-rancher renovate-rancher bot force-pushed the renovate/main-all-minor-patch branch 4 times, most recently from e6f7e41 to 6716a7c Compare April 9, 2025 04:38
@renovate-rancher renovate-rancher bot force-pushed the renovate/main-all-minor-patch branch 3 times, most recently from 6b2f5b4 to d925367 Compare May 7, 2025 04:38
@renovate-rancher renovate-rancher bot force-pushed the renovate/main-all-minor-patch branch 3 times, most recently from 534c61e to c1472c3 Compare May 20, 2025 04:38
@renovate-rancher renovate-rancher bot force-pushed the renovate/main-all-minor-patch branch 2 times, most recently from e843bb1 to ac1ccac Compare May 31, 2025 04:38
@renovate-rancher renovate-rancher bot force-pushed the renovate/main-all-minor-patch branch 5 times, most recently from 6745194 to 1af2932 Compare June 12, 2025 04:41
@renovate-rancher renovate-rancher bot force-pushed the renovate/main-all-minor-patch branch from 1af2932 to f47a910 Compare June 18, 2025 04:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants