Skip to content

Bump the franz-go group across 1 directory with 3 updates #36886

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump the franz-go group across 1 directory with 3 updates #36886

wants to merge 1 commit into from
+9 −9

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 12, 2025 •
edited
Loading

Bumps the franz-go group with 2 updates in the / directory: github.com/twmb/franz-go and github.com/twmb/franz-go/pkg/kadm.

Updates github.com/twmb/franz-go from 1.18.2-0.20250413173443-1d5a55fa468d to 1.19.1

Changelog

Sourced from github.com/twmb/franz-go's changelog.

v1.19.1

This release fixes a very old bug that finally started being possible to hit in v1.19.0. The v1.19.0 release does not work for Kafka versions pre-4.0. This release fixes that (by fixing the bug that has existed since Kafka 2.4) and adds a GH action to test against Kafka 3.8 to help prevent regressions against older brokers as this library marches forward.

  • 50aa74f1 kgo bugfix: ApiVersions replies only with key 18, not all keys

v1.19.0

This is the largest release of franz-go yet. The last patch release was Jan 20, '25. The last minor release was Oct 14, '24.

A big reason for delays the past few month+ has been from spin looping tests and investigating any issue that popped up. Another big delay is that Kafka has a full company adding features -- some questionable -- and I'm one person that spent a significant amount of time catching this library up with the latest Kafka release. Lastly, Kafka released Kafka v3.9 three weeks after my last major release, and simultaneously, a few requests came in for new features in this library that required a lot of time. I wanted a bit of a break and only resumed development more seriously in late Feb. This release is likely >100hrs of work over the last ~4mo, from understanding new features and implementing them, reviewing PRs, and debugging rare test failures.

The next Kafka release is poised to implement more large features (share groups), which unfortunately will mean even more heads down time trying to bolt in yet another feature to an already large library. I hope that Confluent chills with introducing massive client-impacting changes; they've introduced more in the past year than has been introduced from 2019-2023.

Bug fixes / changes / deprecations

  • The BasicLogger will no longer panic if only a single key (no val) is used. Thanks @​vicluq!

  • An internal coding error around managing fetch concurrency was fixed. Thanks @​iimos!

  • Some off by ones with retries were fixed (tldr: we retried one fewer times than configured)

  • AllowAutoTopicCreation and ConsumeRegex can now be used together. Previously, topics would not be created if you were producing and consuming from the same client AND if you used the ConsumeRegex option.

  • A data race in the consumer code path has been fixed. The race is hard to encounter (which is why it never came up even in my weeks of spin-looping tests with -race). See [PR #984](twmb/franz-go#984) for more details.

... (truncated)

Commits

Updates github.com/twmb/franz-go/pkg/kadm from 1.12.0 to 1.16.0

Changelog

Sourced from github.com/twmb/franz-go/pkg/kadm's changelog.

v1.16.0

This release contains a few minor APIs and internal improvements and fixes two minor bugs.

One new API that is introduced also fixes a bug. API-wise, the SaramaHasher was actually not a 1:1 compatible hasher. The logic was identical, but there was a rounding error because Sarama uses int32 module arithmetic, whereas kgo used int (which is likely int64) which caused a different hash result. A new SaramaCompatHasher has been introduced and the old SaramaHasher has been deprecated.

The other bugfix is that OptValue on the kgo.Logger option panicked if you were not using a logger. That has been fixed.

The only other APIs that are introduced are in the kversions package; they are minor, see the commit list below.

If you issue a sharded request and any of the responses has a retryable error in the response, this is no-longer returned as a top-level shard error. The shard error is now nil, and you can properly inspect the response fully.

Lastly (besides other internal minor improvements not worth mentioning), metadata fetches can now inject fake fetches if the metadata response has topic or partition load errors. This is unconditionally true for non-retryable errors. If you use KeepRetryableFetchErrors, you can now also see when metadata fetching is showing unknown topic errors or other retryable errors.

  • a2340eb improvement pkg/kgo: inject fake fetches on metadata load errors
  • d07efd9 feature kversion: add VersionStrings, FromString, V3_6_0
  • 8d30de0 bugfix pkg/kgo: fix OptValue with no logger set
  • 012cd7c improvement kgo: do not return response ErrorCode's as shard errors
  • 1dc3d40 bugfix: actually have correct sarama compatible hasher (thanks @​C-Pro)

v1.15.4

This patch release fixes a difficult to encounter, but fatal-for-group-consuming bug.

The sequence of events to trigger this bug:

  • OffsetCommit is issued before Heartbeat
  • The coordinator for the group needs to be loaded (so, likely, a previous NOT_COORDINATOR error was received)
  • OffsetCommit triggers the load
  • a second OffsetCommit happens while the first is still running, canceling the first OffsetCommit's context

In this sequence of events, FindCoordinator will fail with context.Canceled and, importantly, also return that error to Heartbeat. In the guts of the client, a context.Canceled error should only happen when a group is being

... (truncated)

Commits
  • c1a3c3d Merge pull request #664 from twmb/changelog-v1.16
  • b02fa4d CHANGELOG: note incoming v1.16
  • 7584d23 Merge pull request #665 from twmb/patches-setoffsets-revert
  • 405d87d Revert "pkg/kgo: remove SetOffsets restriction of "only previously polled par...
  • b45f393 kgo: show SetOffsets behavior problem
  • a8e33ff Merge pull request #662 from twmb/patches
  • 0b3766d Merge pull request #622 from C-Pro/sarama-compat-partitioner
  • 3e6d9f9 Merge pull request #663 from twmb/go1.19
  • 636b45c kgo testing: add UnknownTopicRetries(-1)
  • c07b329 pkg/kgo: elide broker log line if context is canceled
  • Additional commits viewable in compare view

Updates github.com/twmb/franz-go/pkg/kmsg from 1.11.2-0.20250413173443-1d5a55fa468d to 1.11.2

Changelog

Sourced from github.com/twmb/franz-go/pkg/kmsg's changelog.

v1.11.2

This patch release fixes HookFetchRecordUnbuffered never being called if a hook also implemented HookFetchRecordBuffered. No existing plugin currently implements these hooks (though one will soon), so this patch is only relevant to you if you manually have added these hooks.

  • 2a37df9 bugfix kgo: patch HookFetchRecordUnbuffered

v1.11.1

This patch release fixes a bug in ConsumePreferringLagFn. The code could panic if you:

  • Consumed from two+ topics
  • Two of the topics have a different amount of partitions
  • The single-partition topic has some lag, the topic with more partitions has one partition with no lag, and another partition with more lag than the single-partition topic

In this case, the code previously would create a non-existent partition to consume from for the single-partition topic and this would immediately result in a panic when the fetch request was built.

See the commit for more details.

  • 38f2ec6 bugfix pkg/kgo: bugfix ConsumePreferringLagFn

v1.11.0

This is a small release containing two minor features and a few behavior improvements. The MarkedOffsets function allows for manually committing marked offsets if you override OnPartitionsRevoked, and UnsafeAbortBufferedRecords allows for forcefully dropping anything being produced (albeit with documented caveats and downsides)

The client now guards against a broker that advertises FetchRequest v13+ (which only uses TopicIDs) but does not actually return / use TopicIDs. If you have an old IBP configured, the broker will not use TopicIDs even if the broker indicates it should. The client will now pin fetching to a max version of 12 if a topic has no TopicID.

The client now sets a record's Topic field earlier to DefaultProduceTopic, which allows the Topic field to be known present (or known non-present) in the OnRecordBuffered hook.

... (truncated)

Commits

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added changelog/no-changelog dependencies PRs that bump a dependency dependencies-go PRs that bump a go dependency team/triage labels May 12, 2025
@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label May 12, 2025
@github-actions github-actions bot requested review from a team as code owners May 12, 2025 20:17
@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented May 12, 2025 •
edited
Loading

Uncompressed package size comparison

Comparison with ancestor 838113127a6ce174f25e2c767accdbb01fd17504

Size reduction summary
package diff status size ancestor threshold
datadog-agent-x86_64-rpm -0.00MB ✅ 782.44MB 782.44MB 0.50MB
datadog-agent-x86_64-suse -0.00MB ✅ 782.44MB 782.44MB 0.50MB
datadog-agent-amd64-deb -0.00MB ✅ 773.49MB 773.49MB 0.50MB
Diff per package
package diff status size ancestor threshold
datadog-agent-aarch64-rpm 0.00MB ✅ 768.37MB 768.37MB 0.50MB
datadog-agent-arm64-deb 0.00MB ✅ 759.44MB 759.44MB 0.50MB
datadog-dogstatsd-amd64-deb 0.00MB ✅ 31.99MB 31.99MB 0.50MB
datadog-dogstatsd-x86_64-rpm 0.00MB ✅ 32.07MB 32.07MB 0.50MB
datadog-dogstatsd-x86_64-suse 0.00MB ✅ 32.07MB 32.07MB 0.50MB
datadog-dogstatsd-arm64-deb 0.00MB ✅ 30.47MB 30.47MB 0.50MB
datadog-heroku-agent-amd64-deb 0.00MB ✅ 380.18MB 380.18MB 0.50MB
datadog-iot-agent-amd64-deb 0.00MB ✅ 62.80MB 62.80MB 0.50MB
datadog-iot-agent-x86_64-rpm 0.00MB ✅ 62.88MB 62.88MB 0.50MB
datadog-iot-agent-x86_64-suse 0.00MB ✅ 62.88MB 62.88MB 0.50MB
datadog-iot-agent-arm64-deb 0.00MB ✅ 59.37MB 59.37MB 0.50MB
datadog-iot-agent-aarch64-rpm 0.00MB ✅ 59.46MB 59.46MB 0.50MB

Decision

✅ Passed

@cit-pr-commenter cit-pr-commenter
Copy link

cit-pr-commenter bot commented May 12, 2025 •
edited
Loading

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 47fbf08b-bf1a-4cd7-ab3d-2fcac29cc3c9

Baseline: e7b7917
Comparison: 25db3fc
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
➖ quality_gate_logs % cpu utilization +3.60 [+0.77, +6.43] 1 Logs bounds checks dashboard
➖ uds_dogstatsd_20mb_12k_contexts_20_senders memory utilization +1.13 [+1.08, +1.18] 1 Logs
➖ file_tree memory utilization +1.00 [+0.80, +1.20] 1 Logs
➖ tcp_syslog_to_blackhole ingress throughput +0.88 [+0.82, +0.94] 1 Logs
➖ ddot_metrics memory utilization +0.38 [+0.26, +0.50] 1 Logs
➖ quality_gate_idle memory utilization +0.23 [+0.15, +0.30] 1 Logs bounds checks dashboard
➖ docker_containers_memory memory utilization +0.22 [+0.11, +0.32] 1 Logs
➖ file_to_blackhole_0ms_latency_http1 egress throughput +0.06 [-0.48, +0.61] 1 Logs
➖ file_to_blackhole_1000ms_latency egress throughput +0.05 [-0.60, +0.69] 1 Logs
➖ file_to_blackhole_0ms_latency egress throughput +0.04 [-0.55, +0.64] 1 Logs
➖ file_to_blackhole_500ms_latency egress throughput +0.03 [-0.56, +0.62] 1 Logs
➖ file_to_blackhole_1000ms_latency_linear_load egress throughput +0.02 [-0.21, +0.26] 1 Logs
➖ tcp_dd_logs_filter_exclude ingress throughput +0.01 [-0.02, +0.04] 1 Logs
➖ file_to_blackhole_300ms_latency egress throughput +0.00 [-0.62, +0.63] 1 Logs
➖ file_to_blackhole_0ms_latency_http2 egress throughput +0.00 [-0.54, +0.55] 1 Logs
➖ uds_dogstatsd_to_api ingress throughput -0.01 [-0.27, +0.26] 1 Logs
➖ file_to_blackhole_100ms_latency egress throughput -0.04 [-0.64, +0.56] 1 Logs
➖ otlp_ingest_metrics memory utilization -0.14 [-0.30, +0.01] 1 Logs
➖ ddot_logs memory utilization -0.36 [-0.48, -0.24] 1 Logs
➖ quality_gate_idle_all_features memory utilization -0.38 [-0.47, -0.28] 1 Logs bounds checks dashboard
➖ docker_containers_cpu % cpu utilization -0.55 [-3.55, +2.45] 1 Logs
➖ otlp_ingest_logs memory utilization -0.66 [-0.79, -0.53] 1 Logs
➖ uds_dogstatsd_to_api_cpu % cpu utilization -2.46 [-3.30, -1.62] 1 Logs

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed links
✅ docker_containers_cpu simple_check_run 10/10
✅ docker_containers_memory memory_usage 10/10
✅ docker_containers_memory simple_check_run 10/10
✅ file_to_blackhole_0ms_latency lost_bytes 10/10
✅ file_to_blackhole_0ms_latency memory_usage 10/10
✅ file_to_blackhole_0ms_latency_http1 lost_bytes 10/10
✅ file_to_blackhole_0ms_latency_http1 memory_usage 10/10
✅ file_to_blackhole_0ms_latency_http2 lost_bytes 10/10
✅ file_to_blackhole_0ms_latency_http2 memory_usage 10/10
✅ file_to_blackhole_1000ms_latency memory_usage 10/10
✅ file_to_blackhole_1000ms_latency_linear_load memory_usage 10/10
✅ file_to_blackhole_100ms_latency lost_bytes 10/10
✅ file_to_blackhole_100ms_latency memory_usage 10/10
✅ file_to_blackhole_300ms_latency lost_bytes 10/10
✅ file_to_blackhole_300ms_latency memory_usage 10/10
✅ file_to_blackhole_500ms_latency lost_bytes 10/10
✅ file_to_blackhole_500ms_latency memory_usage 10/10
✅ quality_gate_idle intake_connections 10/10 bounds checks dashboard
✅ quality_gate_idle memory_usage 10/10 bounds checks dashboard
✅ quality_gate_idle_all_features intake_connections 10/10 bounds checks dashboard
✅ quality_gate_idle_all_features memory_usage 10/10 bounds checks dashboard
✅ quality_gate_logs intake_connections 10/10 bounds checks dashboard
✅ quality_gate_logs lost_bytes 10/10 bounds checks dashboard
✅ quality_gate_logs memory_usage 10/10 bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

  • quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.

@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented May 12, 2025 •
edited
Loading

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor e7b7917

Successful checks

Info

Quality gate Delta On disk size (MiB) Delta On wire size (MiB)
✅ agent_deb_amd64 $${0}$$ $${697.02}$$ < $${697.37}$$ $${+0.05}$$ $${176.16}$$ < $${177.03}$$
✅ agent_deb_amd64_fips $${0}$$ $${695.31}$$ < $${695.59}$$ $${+0}$$ $${175.54}$$ < $${176.51}$$
✅ agent_heroku_amd64 $${0}$$ $${358.67}$$ < $${359.67}$$ $${-0}$$ $${96.51}$$ < $${97.47}$$
✅ agent_msi $${0}$$ $${958.88}$$ < $${959.86}$$ $${+0.02}$$ $${146.3}$$ < $${147.27}$$
✅ agent_rpm_amd64 $${0}$$ $${697.0}$$ < $${697.36}$$ $${+0}$$ $${177.69}$$ < $${178.56}$$
✅ agent_rpm_amd64_fips $${0}$$ $${695.3}$$ < $${695.58}$$ $${-0.01}$$ $${177.51}$$ < $${178.43}$$
✅ agent_rpm_arm64 $${0}$$ $${687.03}$$ < $${687.37}$$ $${+0.03}$$ $${161.11}$$ < $${161.99}$$
✅ agent_rpm_arm64_fips $${0}$$ $${685.43}$$ < $${685.72}$$ $${+0.03}$$ $${160.27}$$ < $${161.11}$$
✅ agent_suse_amd64 $${0}$$ $${697.0}$$ < $${697.36}$$ $${+0}$$ $${177.69}$$ < $${178.56}$$
✅ agent_suse_amd64_fips $${0}$$ $${695.3}$$ < $${695.58}$$ $${-0.01}$$ $${177.51}$$ < $${178.43}$$
✅ agent_suse_arm64 $${0}$$ $${687.03}$$ < $${687.37}$$ $${+0.03}$$ $${161.11}$$ < $${161.99}$$
✅ agent_suse_arm64_fips $${0}$$ $${685.43}$$ < $${685.72}$$ $${+0.03}$$ $${160.27}$$ < $${161.11}$$
✅ docker_agent_amd64 $${-0}$$ $${780.8}$$ < $${781.16}$$ $${-0}$$ $${268.79}$$ < $${269.63}$$
✅ docker_agent_arm64 $${-0}$$ $${794.28}$$ < $${794.62}$$ $${-0}$$ $${256.14}$$ < $${257.0}$$
✅ docker_agent_jmx_amd64 $${-0}$$ $${972.0}$$ < $${972.35}$$ $${+0.01}$$ $${337.77}$$ < $${338.6}$$
✅ docker_agent_jmx_arm64 $${+0}$$ $${974.07}$$ < $${974.41}$$ $${+0}$$ $${321.08}$$ < $${321.97}$$
✅ docker_agent_windows1809 $${+0.07}$$ $${1487.03}$$ < $${1488.0}$$ $${-0.04}$$ $${487.99}$$ < $${488.95}$$
✅ docker_agent_windows1809_core $${-0}$$ $${6216.98}$$ < $${6218.0}$$ $${0}$$ $${2048.0}$$ < $${2049.0}$$
✅ docker_agent_windows1809_core_jmx $${-0.2}$$ $${6338.56}$$ < $${6361.0}$$ $${0}$$ $${2048.0}$$ < $${2049.0}$$
✅ docker_agent_windows1809_jmx $${+0}$$ $${1608.66}$$ < $${1609.5}$$ $${+0.05}$$ $${530.34}$$ < $${531.32}$$
✅ docker_agent_windows2022 $${-0.05}$$ $${1506.13}$$ < $${1507.0}$$ $${-0.01}$$ $${500.75}$$ < $${501.7}$$
✅ docker_agent_windows2022_core $${-0.22}$$ $${6190.05}$$ < $${6311.0}$$ $${0}$$ $${2048.0}$$ < $${2049.0}$$
✅ docker_agent_windows2022_core_jmx $${-0.3}$$ $${6311.69}$$ < $${6313.0}$$ $${0}$$ $${2048.0}$$ < $${2049.0}$$
✅ docker_agent_windows2022_jmx $${+0.07}$$ $${1627.91}$$ < $${1628.16}$$ $${-0.02}$$ $${543.02}$$ < $${543.98}$$
✅ docker_cluster_agent_amd64 $${+0}$$ $${212.84}$$ < $${213.79}$$ $${-0}$$ $${72.38}$$ < $${73.33}$$
✅ docker_cluster_agent_arm64 $${0}$$ $${228.68}$$ < $${229.64}$$ $${+0}$$ $${68.65}$$ < $${69.6}$$
✅ docker_cws_instrumentation_amd64 $${0}$$ $${7.08}$$ < $${7.12}$$ $${-0}$$ $${2.95}$$ < $${3.29}$$
✅ docker_cws_instrumentation_arm64 $${0}$$ $${6.69}$$ < $${6.92}$$ $${-0}$$ $${2.7}$$ < $${3.07}$$
✅ docker_dogstatsd_amd64 $${-0}$$ $${39.22}$$ < $${39.57}$$ $${-0}$$ $${15.12}$$ < $${15.76}$$
✅ docker_dogstatsd_arm64 $${+0}$$ $${37.88}$$ < $${38.2}$$ $${+0}$$ $${14.53}$$ < $${14.83}$$
✅ dogstatsd_deb_amd64 $${0}$$ $${30.45}$$ < $${31.4}$$ $${-0}$$ $${8.0}$$ < $${8.95}$$
✅ dogstatsd_deb_arm64 $${0}$$ $${29.02}$$ < $${29.97}$$ $${-0}$$ $${6.94}$$ < $${7.89}$$
✅ dogstatsd_rpm_amd64 $${0}$$ $${30.45}$$ < $${31.4}$$ $${-0}$$ $${8.01}$$ < $${8.96}$$
✅ dogstatsd_suse_amd64 $${0}$$ $${30.45}$$ < $${31.4}$$ $${-0}$$ $${8.01}$$ < $${8.96}$$
✅ iot_agent_deb_amd64 $${0}$$ $${50.43}$$ < $${51.38}$$ $${+0}$$ $${12.84}$$ < $${13.79}$$
✅ iot_agent_deb_arm64 $${0}$$ $${47.9}$$ < $${48.85}$$ $${+0}$$ $${11.14}$$ < $${12.09}$$
✅ iot_agent_deb_armhf $${0}$$ $${47.47}$$ < $${48.42}$$ $${+0.01}$$ $${11.21}$$ < $${12.16}$$
✅ iot_agent_rpm_amd64 $${0}$$ $${50.43}$$ < $${51.38}$$ $${+0}$$ $${12.86}$$ < $${13.81}$$
✅ iot_agent_rpm_arm64 $${0}$$ $${47.9}$$ < $${48.85}$$ $${+0}$$ $${11.16}$$ < $${12.11}$$
✅ iot_agent_suse_amd64 $${0}$$ $${50.43}$$ < $${51.38}$$ $${+0}$$ $${12.86}$$ < $${13.81}$$

@dependabot dependabot bot force-pushed the dependabot/go_modules/franz-go-26d7059fb3 branch 4 times, most recently from e5634f3 to 83079a6 Compare May 19, 2025 20:15
@dependabot dependabot bot force-pushed the dependabot/go_modules/franz-go-26d7059fb3 branch 2 times, most recently from b498287 to cd8dec3 Compare June 2, 2025 20:10
@dependabot dependabot bot force-pushed the dependabot/go_modules/franz-go-26d7059fb3 branch from cd8dec3 to feb9748 Compare June 9, 2025 20:29
@dependabot
Bump the franz-go group across 1 directory with 3 updates
25db3fc 
Bumps the franz-go group with 2 updates in the / directory: [github.com/twmb/franz-go](https://github.com/twmb/franz-go) and [github.com/twmb/franz-go/pkg/kadm](https://github.com/twmb/franz-go).


Updates `github.com/twmb/franz-go` from 1.18.2-0.20250413173443-1d5a55fa468d to 1.19.1
- [Changelog](https://github.com/twmb/franz-go/blob/master/CHANGELOG.md)
- [Commits](https://github.com/twmb/franz-go/commits/v1.19.1)

Updates `github.com/twmb/franz-go/pkg/kadm` from 1.12.0 to 1.16.0
- [Changelog](https://github.com/twmb/franz-go/blob/master/CHANGELOG.md)
- [Commits](twmb/franz-go@v1.12.0...v1.16.0)

Updates `github.com/twmb/franz-go/pkg/kmsg` from 1.11.2-0.20250413173443-1d5a55fa468d to 1.11.2
- [Changelog](https://github.com/twmb/franz-go/blob/master/CHANGELOG.md)
- [Commits](https://github.com/twmb/franz-go/commits/v1.11.2)

---
updated-dependencies:
- dependency-name: github.com/twmb/franz-go
  dependency-version: 1.19.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: franz-go
- dependency-name: github.com/twmb/franz-go/pkg/kadm
  dependency-version: 1.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: franz-go
- dependency-name: github.com/twmb/franz-go/pkg/kmsg
  dependency-version: 1.11.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: franz-go
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/franz-go-26d7059fb3 branch from feb9748 to 25db3fc Compare June 16, 2025 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
changelog/no-changelog dependencies PRs that bump a dependency dependencies-go PRs that bump a go dependency short review PR is simple enough to be reviewed quickly team/triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants