Skip to content

Use the PubSub.Sender behavior for fastlaning - #6844

Merged
SteffenDE merged 5 commits into
mainfrom
sd-pubsub-sender
Oct 7, 2026
Merged

SteffenDE merged 5 commits into
mainfrom
sd-pubsub-sender

Conversation

@SteffenDE

@SteffenDE SteffenDE commented Sep 17, 2026 •

Copy link
Copy Markdown
Member

Updating to 1.9 should be done with 1.8.16 or later in between, see #6869.

Relates to phoenixframework/phoenix_pubsub#218.

Since we want to provide people with a way to update without crashing
old nodes, we still send the dispatcher and will remove it in 1.10.
Comment thread mix.exs Outdated
Comment thread installer/templates/phx_umbrella/apps/app_name/mix.exs.eex Outdated
@SteffenDE
SteffenDE requested a review from josevalim October 5, 2026 17:14
Comment thread lib/phoenix/presence.ex Outdated
@josevalim

Copy link
Copy Markdown
Member

The other option is to add sender to 1.8.X and then include a notice in the changelog that people need to update to latest patch release before updating to 1.9.

I'd go down this route. I assume it is a matter of merging this into v1.8 and a prunned version on main?

@SteffenDE

Copy link
Copy Markdown
Member Author

It depends if we want to also bump the pubsub requirement on 1.8.X, otherwise we need some compile time checks.

@josevalim

Copy link
Copy Markdown
Member

Bumping the pubsub version should be fine, yes! It is all backwards compatible.

@SteffenDE
SteffenDE merged commit 2b12377 into main Oct 7, 2026
25 checks passed
@SteffenDE
SteffenDE deleted the sd-pubsub-sender branch October 7, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants