chore(deps): bump phoenix_pubsub from 2.3.0 to 2.4.0

[dependabot]

Bumps phoenix_pubsub from 2.3.0 to 2.4.0.

Changelog

Sourced from phoenix_pubsub's changelog.

2.4.0 (2026-10-07)

Enhancements

• Add Phoenix.PubSub.Sender as a successor for custom dispatchers
• Add Phoenix.PubSub.unsubscribe_sender/3 to selectively remove sender subscriptions

Migrating custom dispatchers

Custom dispatchers and the :metadata subscription option are deprecated in favor of per-subscription senders. Existing dispatchers continue to work, except that subscribing with :metadata in the shape of [atom | term] now raises. That shape is reserved for senders.

To migrate:

1. Implement the Phoenix.PubSub.Sender behaviour in your delivery module. Its send/4 callback receives one subscriber pid, its metadata, the message, and an accumulator. Move the delivery logic from dispatch/3 into this callback. PubSub handles iterating over subscribers and excluding the originating pid for broadcast_from calls.

2. Replace metadata: metadata in subscriptions with sender: {MySender, metadata}:

   Phoenix.PubSub.subscribe(MyApp.PubSub, "topic", sender: {MySender, metadata})

3. Remove custom dispatcher arguments from broadcast calls and remove the :dispatcher option from your PubSub child specification to use the default Phoenix.PubSub dispatcher. Custom dispatchers control delivery themselves and do not automatically invoke senders, so changing subscriptions alone is not sufficient.

4. Replace unsubscribe_match/3 calls for migrated subscriptions with unsubscribe_sender/3, passing the same sender tuple:

   Phoenix.PubSub.unsubscribe_sender(MyApp.PubSub, "topic", {MySender, metadata})

Commits

• 9134531 Release v2.4.0
• 76f64f9 Merge pull request #219 from phoenixframework/sd-sender-2
• be1aa34 add note about reserved metadata shape and re-add guards
• 1527c10 use OTP 29 for main, fmt
• 5b81eae add Elixir 1.20 + OTP 29 to CI
• 12ff0ef check formatter in CI
• 8b1ca0b Run the formatter
• 441201d Prepare 2.4.0
• 0d813c5 provide a new mechanism for custom message sending
• See full diff in compare view

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)

---

📌 TL;DR

This PR updates the phoenix_pubsub dependency from version 2.3.0 to 2.4.0 in the project's lock file. This is a routine dependency maintenance change to ensure the application uses the latest stable release of the PubSub library.

🎯 Type of Change

• 🚀 New feature
• 🐛 Bugfix
• 🧹 Refactor
• ⚡ Performance
• 📚 Documentation
• ⚙️ CI / Configuration

🔍 Changes Walkthrough

File	Summary of Changes
mix.lock	Updated the locked version of the phoenix_pubsub package from 2.3.0 to 2.4.0, including the corresponding hex checksum and metadata.

📊 Architectural Flow

(Omitted: This change is a dependency version bump in a lock file and does not alter component interactions, APIs, or workflow state.)

[claude]

⚠️ Code review skipped — your organization has no extra usage available to pay for this review.

If your organization's extra usage balance is empty, an organization admin can add extra usage credits at claude.ai/admin-settings/usage. If its monthly spend limit was reached, an admin can raise it on the same page. If neither applies, contact Anthropic support.

Once extra usage is available, someone with write access to this repository can comment @claude review on this pull request to trigger a review.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 182ef202-05d7-4903-9968-36313e34cd04

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[dos]

⏱️ Code Review completed (1 files · 3,420 chars · 1 PR unit(s))

✅ CLEAN_PASS: No candidate issues flagged

NO_ISSUES: The diff is a standard dependency lock file update with no functional code changes to review.