build(deps): bump the franz-go group across 1 directory with 3 updates

[dependabot]

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.20.7 to 1.21.6

Changelog

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

v1.21.6

Some bug fixes (mostly minor - hence the delay for the release) found by users and further Claude audits. I am gearing up for a 1.22 release but some of the features I am planning for are more complicated to review, so it may take a bit of time. Anyway:

• Previously, rollback from a cooperative group to an eager group was deliberately not supported and there was a data race condition if this happened. It is now technically supported, although you will experience duplicate data. If you want a safe non-duplicate-causing rollback, you need to turn off the entire group, remove the cooperative consumer, and swap the whole group to eager rebalancing.

• Fixed a panic: close of closed channel on an acks=0 produce connection in a specific edge case (a broker connection dying before the connection was fully established caused the panic).

• If EndTransaction failed with an unconfirmed outcome (a transport error, exhausted retries, or UNKNOWN_SERVER_ERROR), the documented abort retry was a wire no-op and the next transaction could silently commit the prior "failed" transaction's records under KIP-890 part 2. The producer ID is now flagged for reload, which fence-aborts anything still ongoing broker-side.

• GroupTransactSession.End could hang forever, ignoring its context, if the group had never joined (e.g. the consumed topic did not exist yet) and the transaction committed no offsets.

• Previously, if a broker replied to ApiVersions with an error, we ignored it and you would eventually see an unclear error (usually a bare io.EOF, since anything that rejects ApiVersions hangs up right after replying). These errors are now handled correctly.

• Some niche edge case bugs that are only worth reading about if you're super interested were found in repeated Claude audits and were fixed (check the PR / git history). This includes further KIP-848 "next gen consumer group" fixes.

Relevant commits

• 582e0f21 bugfix kgo: surface error codes in ApiVersions responses
• 67ef4c61 bugfix kgo: fix double close of a connection's deadCh on acks=0 produce
• 3ac2fff1 bugfix kgo: revoke everything when the group protocol downgrades from cooperative to eager
• 795d5b61 improvement kgo: flatten topic/partition maps in group rebalance logs (thanks @​constanca-m!)
• 70addc1e improvement kgo: classify retired broker reads as broker dead (thanks @​tomplarge!)
• 18f9a10f improvement deps: replace golang.org/x/crypto/pbkdf2 with stdlib crypto/pbkdf2 (thanks @​macdewee!)
• 6ecd2f9f bugfix kgo: recover when an attempted EndTxn outcome is unconfirmed
• 821f879e bugfix kgo: fix GroupTransactSession.End hanging when the group never joined

v1.21.5

... (truncated)

Commits

• b881450 Merge pull request #1383 from twmb/cl
• 34e5c63 update changelog for incoming v1.21.6
• b8e7523 Merge pull request #1382 from twmb/kgo-drop-software-name-validation
• b044036 kgo: drop client-side software name/version validation
• adb3a18 Merge pull request #1381 from twmb/kgo-apiversions-error-code
• 582e0f2 kgo: surface error codes in ApiVersions responses
• cc159eb Merge pull request #1380 from RafalKorepta/rk/bump-klauspost-compress-dep
• 481c394 deps: bump github.com/klauspost/compress to v1.18.7
• 4176fc0 Merge pull request #1376 from twmb/record-path-allocs
• 0289a55 kgo: reduce allocations on the fetch and produce paths
• Additional commits viewable in compare view

Updates github.com/twmb/franz-go/pkg/kadm from 1.17.2 to 1.18.0

Changelog

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

v1.18.0

This release adds support for Kafka 3.7, adds a few community requested APIs, some internal improvements, and fixes two bugs. One of the bugfixes is for a deadlock; it is recommended to bump to this release to ensure you do not run into the deadlock. The features in this release are relatively small.

This adds protocol support for KIP-890 and KIP-994, and adds further protocol support for [KIP-848][KIP-848]. If you are using transactions, you may see a new kerr.TransactionAbortable error, which signals that your ongoing transaction should be aborted and will not be successful if you try to commit it.

Lastly, there have been a few improvements to pkg/sr that are not mentioned in these changelog notes.

Bug fixes

• If you canceled the context used while producing while your client was at the maximum buffered records or bytes, it was possible to experience deadlocks. This has been fixed. See #832 for more details.

• Previously, if using GetConsumeTopics while regex consuming, the function would return all topics ever discovered. It now returns only the topics that are being consumed.

Improvements

• The client now internaly ignores OutOfOrderSequenceNumber errors that are encountered when consuming if possible. If a producer produces very infrequently, it is possible the broker forgets the producer by the next time the producer produces. In this case, the producer receives an OutOfOrderSequenceNumber error. The client now internally resets properly so that you do not see the error.

Features

• AllowRebalance and CloseAllowingRebalance have been added to GroupTransactSession.
• The FetchTopic type now has includes the topic's TopicID.
• The ErrGroupSession internal error field is now public, allowing you to test how you handle the internal error.
• You may now receive a kerr.TransactionAbortable error from many functions while using transactions.

Relevant commits

• 0fd1959d kgo: support Kafka 3.8's kip-890 modifications
• 68163c55 bugfix kgo: do not add all topics to internal tps map when regex consuming
• 3548d1f7 improvement kgo: ignore OOOSN where possible

... (truncated)

Commits

• 0a9996b Merge pull request #841 from twmb/1.18-changelog
• 835c682 CHANGELOG: note incoming release
• d771ddf Merge pull request #838 from twmb/810
• 04356d7 Merge pull request #835 from twmb/819
• 3d71b14 Merge pull request #834 from twmb/805
• 019799a Merge pull request #829 from andrewstucki/sr-client-opts
• 3a0f09a Merge pull request #814 from noamcohen97/new-offset-helper
• 6028e72 Merge pull request #794 from twmb/790
• 581d7ef Merge pull request #789 from sbuliarca/errgroupsession-export-err
• fd084a5 Merge pull request #760 from twmb/753
• Additional commits viewable in compare view

Updates github.com/twmb/franz-go/pkg/kmsg from 1.12.0 to 1.13.1

Changelog

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

v1.13.1

This patch release fixes a bug where a producer could enter a deadlock if a topic is deleted and recreated very quickly while producing.

• 769e02f producer: avoid deadlock when when quickly recreating a topic

v1.13.0

This release contains a few new APIs, two rare bug fixes, updates to plugins, and changes the library to now require 1.18.

Go version

This library has supported Go 1.15 since the beginning. There have been many useful features that this library has not been able to use because of continued backcompat for 1.15. There is really no reason to support such an old version of Go, and Go itself does not support releases prior to 1.18 -- and 1.18 is currently only supported for security backports. Switching to 1.18 allows this library to remove a few 1.15 / 1.16 backcompat files, and allows switching this library from interface{} to any.

Behavior changes

If group consuming fails with an error that looks non-retryable, the error is now injected into polling as a fake errored fetch. Multiple people have ran into problems where their group consumers were failing due to ACLs or due to network issues, and it is hard to detect these failures: you either have to pay close attention to logs, or you have to hook into HookGroupManageError. Now, the error is injected into polling.

Bug fixes

This release contains two bug fixes, one of which is very rare to encounter, and one of which is very easy to encounter but requires configuring the client in a way that (nearly) nobody does.

Rare: If you were using EndAndBeginTransaction, there was an internal race that could result in a deadlock.

Rare configuration: If you configured balancers manually, and you configured CooperativeSticky with any other eager balancer, then the client would internally sometimes think it was eager consuming, and sometimes think it was cooperative consuming. This would result in stuck partitions while consuming.

Features

... (truncated)

Commits

• 1a59c2d Merge pull request #404 from twmb/bugfix
• 5e0ba1c document incoming v1.13.1, update readme, fix golangci-lint
• d984c21 Merge pull request #401 from bgranvea/fix-segment-bench
• 769e02f producer: avoid deadlock when when quickly recreating a topic
• 5c2a90c set async commit
• 8cb298d Merge pull request #399 from twmb/dependabot/go_modules/examples/hooks_and_lo...
• 1141ce4 Merge pull request #397 from twmb/dependabot/go_modules/examples/hooks_and_lo...
• d5ef6e0 Merge pull request #398 from twmb/dependabot/go_modules/examples/bench/google...
• 8215a54 Merge pull request #400 from twmb/dependabot/go_modules/plugin/kprom/google.g...
• 6fdb469 build(deps): bump google.golang.org/protobuf in /plugin/kprom
• Additional commits viewable in compare view