Skip to content

Bump kafka_ex from 0.15.0 to 1.0.1#270

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/hex/kafka_ex-1.0.1
Open

Bump kafka_ex from 0.15.0 to 1.0.1#270
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/hex/kafka_ex-1.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 29, 2026

Copy link
Copy Markdown
Contributor

Bumps kafka_ex from 0.15.0 to 1.0.1.

Release notes

Sourced from kafka_ex's releases.

v1.0.1

What's Changed

New Contributors

Full Changelog: kafkaex/kafka_ex@v1.0.0...v1.0.1

v1.0.0

What's Changed

... (truncated)

Changelog

Sourced from kafka_ex's changelog.

1.0.1 (2026-06-26)

Breaking Changes

  • KafkaEx.API.start_client/1 no longer registers globally by default. Previously start_client() (no :name argument) silently registered the GenServer as KafkaEx.Client, while the documented :name option was ignored. Two callers collided with :already_started.

    Now start_client() returns {:ok, pid} unnamed. To preserve the old behavior explicitly:

    KafkaEx.API.start_client(name: KafkaEx.Client)

    :name accepts any GenServer.name() shape: an atom, {:global, term}, or {:via, Module, term}. See UPGRADING.md for the full migration. Most callers bind the returned pid ({:ok, client} = start_client(...)) and are unaffected.

  • Consumer auto_offset_reset now defaults to :latest (was :none), matching the Kafka/Java client default, and :none now raises instead of silently starting a fresh consumer group from the earliest offset. This only affects a consumer with no valid committed offset that does not set auto_offset_reset explicitly: a new consumer group now consumes only new messages (previously it silently replayed the whole topic), and an out-of-range offset now resets to latest (previously it raised). Set auto_offset_reset: :earliest to keep replaying from the beginning, or :none for the strict raise-on-bad-offset behavior. An invalid value now fails fast at consumer start. See UPGRADING.md.

Fixed

  • KafkaEx.API.start_client/1 and child_spec/1 now merge config.exs defaults and accept the documented :brokers option (#538). Previously start_client(brokers: [...]) crashed with InvalidConsumerGroupError: nil because config defaults were never merged and the :brokers key was ignored (the client read :uris). :brokers is now the canonical key; :uris is a deprecated-but-working alias. start_client/1 returns {:error, :invalid_consumer_group} on a bad group; child_spec/1 raises KafkaEx.InvalidConsumerGroupError at spec-build time.

  • KafkaEx.API.fetch/5 (and KafkaEx.Consumer.Stream) hang at logend. Previously the GenServer.call default timeout (5s) and the per-broker Socket.recv timeout (1-3s from sync_timeout config) were not aligned with the user-supplied :max_wait_time (default 10s). The broker held the long-poll for up to 10s; both upper timeouts fired first, causing socket close → reconnect → retry 3 times, every retry hitting the same mismatch.

... (truncated)

Commits
  • 1bb04ae chore: add AGENTS.md as canonical agent guide; CLAUDE.md symlinks to it (#558)
  • 3228264 fix: terminal-stop on group-authorization failure; drop stale heartbeat-error...
  • a4e3864 fix: drop control batches and advance past them (consumer + stream) (#557)
  • e33abf0 fix: bound broker connect with a timeout instead of blocking indefinitely (#556)
  • c6ba2a7 fix: rejoin (not crash) on illegal_generation/unknown_member_id; terminal-sto...
  • 3651f1f test: eliminate the on_exit teardown :noproc flake class (#553)
  • 4e13020 refactor: rename Retry max_retries option to max_attempts (#552)
  • 4baf532 refactor: ride load_offsets startup retry on Retry.with_retry (#551)
  • cde3b0a fix: offset-commit/fetch correctness (no silent loss / duplicates) (#548)
  • 2d8d9af test: stabilize three flaky consumer-group / config tests (#549)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
Bump kafka_ex from 0.15.0 to 1.0.1
9cc1b07 
Bumps [kafka_ex](https://github.com/kafkaex/kafka_ex) from 0.15.0 to 1.0.1.
- [Release notes](https://github.com/kafkaex/kafka_ex/releases)
- [Changelog](https://github.com/kafkaex/kafka_ex/blob/master/CHANGELOG.md)
- [Commits](kafkaex/kafka_ex@v0.15.0...v1.0.1)

---
updated-dependencies:
- dependency-name: kafka_ex
  dependency-version: 1.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file elixir Pull requests that update elixir code labels Jun 29, 2026
@dependabot dependabot Bot mentioned this pull request Jun 29, 2026
Closed
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

dependencies Pull requests that update a dependency file elixir Pull requests that update elixir code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants