chore: update phoenix_pubsub to 2.3.0 in mix.lock - #30
Open
devin-ai-integration[bot] wants to merge 1 commit into
Open
chore: update phoenix_pubsub to 2.3.0 in mix.lock#30devin-ai-integration[bot] wants to merge 1 commit into
devin-ai-integration[bot] wants to merge 1 commit into
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
Author
|
@cursor review |
keelerm84
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refreshes the committed
mix.lockto the latest versions allowed by the existingmix.exsconstraints; onlyphoenix_pubsubhad a newer release.phoenix_pubsub2.2.0 → 2.3.0 (transitive, only lock entry that moved onmix deps.update --all)mix.exschanges:launchdarkly_server_sdk~> 3.0already locks the latest 3.11.2, and every other dep is already at latest-within-constraintmix compile --warnings-as-errorsis cleanImplementation details
Built and run in
docker run elixir:1.17-otp-26(no Elixir on the test machine):mix deps.update --all→ single lock change (phoenix_pubsub 2.3.0)mix compile --warnings-as-errors→ cleanmix test→ 3 tests, 0 failuresLD_SDK_KEY=<hello-apps server key> mix phx.server→ streaming connection established,/hello-launchdarkly/Joerenders (screenshot above)Notes / not fixed here:
alternate.pageflag (onlyhello-boolean), so the SDK logsUnknown feature flag "alternate.page"; returning default valueand the page shows the default (non-alternate) variation. This is an environment-data gap, not a code issue.mix deps.getreports security advisories forcowlib2.19.0 andgun2.5.0, both pulled in transitively viashotgun←launchdarkly_server_sdk. No fixed releases exist within the allowed ranges, so nothing to change repo-side.mix formatcannot run in this repo (.formatter.exsimports:ecto, which is not a dependency); pre-existing.Link to Devin session: https://app.devin.ai/sessions/10d6310decae4a1092f0aa85b16d9af4
Open in Devin Desktop: https://app.devin.ai/desktop/session/10d6310decae4a1092f0aa85b16d9af4?variant=devin
Note
Overview
Updates
mix.lockonly:phoenix_pubsub2.2.0 → 2.3.0 (checksum and lock metadata updated). There are nomix.exsor application code changes—this is the resolved version Phoenix already allows via~> 2.1.This is a routine transitive dependency refresh (e.g. after
mix deps.update --all); behavior should stay the same aside from whatever fixes ship in 2.3.0.Reviewed by Cursor Bugbot for commit 8136414. Bugbot is set up for automated code reviews on this repo. Configure here.