Deps: phoenix family + misc freshness - #188
Merged
Merged
Conversation
Phoenix 1.8.13, LiveView 1.2.11, LiveDashboard 0.9.0, telemetry_metrics 1.2.0, pubsub 2.3.0 moved as a coupled set; plus improv 0.1.3 (bluez ~> 0.2), req 0.7.4, ssh_subsystem_fwup 0.6.8, and doc/toolchain patches. Lock-only; all constraints already admit these. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Deliberate freshness pass for the deps that transiently appeared during the v0.1.10 resolution — same versions, now pinned via an explicit
mix.exsedit + scopedmix deps.updateinstead of an incidental side effect.Coupled Phoenix family (moved together):
phoenix1.8.11 → 1.8.13 — bug fixes only:phx.gen.authreturn_tosession-key clear, a channel-message-drop regression (introduced 1.8.3), and a Chrome 149 tab-resume reconnect workaround.phoenix_live_view1.2.9 → 1.2.11 — bug fixes (upload/hook/JS-transition edge cases) + enhancements (navigation_type/2, dynamicphx-hook, external-upload cancel-on-navigate). No breaking changes for this app's usage.phoenix_live_dashboard0.8.0 → 0.9.0 (minor, mix.exs constraint bumped~> 0.8→~> 0.9) — see verdict below.phoenix_pubsub2.2.0 → 2.3.0 — adds:group_byRegistry-sharding option and a configurable default:dispatcher(both opt-in, unused here), plus a tracker-state cleanup bug fix.Phoenix.PubSub.Supervisorinternals changed (registry:keyscomputed from:group_by) but default behavior (:pid/:duplicate) is unchanged.telemetry_metrics1.1.0 → 1.2.0 — adds function support for:tags(supersedes:tag_values); no removal, existing config still works.Plus:
improv0.1.2 → 0.1.3 (our own lib) — pure constraint bump,{:bluez, "~> 0.1"}→{:bluez, "~> 0.2"}. No code changes. bluez was already locked at 0.2.0.req0.7.2 → 0.7.4 — 0.7.3 reverted the "auto GET→POST when body is set" behavior added in 0.7.0 (restores plain GET semantics); 0.7.4 allows explicit duplicate query params input_paramsand fixesput_path_paramsoverwriting redirect targets. Not used in a way that depended on the reverted behavior.ssh_subsystem_fwup0.6.7 → 0.6.8 — improves UUID-nickname/error visibility inmix upload; no functional change to the proxy.nerves_toolchain_x86_64_nerves_linux_musl15.3.0 → 15.3.1 — build-script/mirror-URL patches only (matches the toolchain bump already shipped for the other 4 targets in Deps: nerves_discovery 0.1.4 + toolchains 15.3.1 #186).phoenix_live_dashboard0.9.0 changelog verdict — no action neededFull delta (
mix hex.package diff phoenix_live_dashboard 0.8.0..0.9.0, CHANGELOG hunk):(plus the intervening 0.8.1–0.8.7 patch entries, all bug fixes)
/dashboardroute (dev-onlylive_dashboard "/dashboard"mount, not user-facing), so no impact on the Overview/Audio/etc. app pages.info_moduleoverride doesn't apply — this app has no Ecto repo configured.mix.exsconstraint bumped from"~> 0.8"to"~> 0.9"since the lock was already (harmlessly) sitting at 0.9.0 ahead of that constraint from the v0.1.10 resolution — this PR makes that consistent again.diff.hex.pm links
mix.lockdiff (only these 8 rows changed)(
phoenix_live_dashboardwas already locked at 0.9.0; only itsmix.exsconstraint needed the edit.)No
assets/package.json-driven npm install applies — this is a Nerves-embedded Phoenix app;assets/package.jsononly hasfile:../deps/...local references (no npm registry deps, no lockfile, nonpm/nodein the toolchain), so it's untouched.Gate results
mix format --check-formatted— cleanmise exec -- sh -c 'MIX_TARGET=host mix compile --warnings-as-errors --force'— clean (only pre-existing, unrelated vendoredmdns_litewarnings, which aren't part of this app's own compile and don't fail the build)mise run test— 1607/1607 passed (2 doctests, 1605 tests, 3 excluded) on the final run. One earlier run showed a single flake (UniversalProxy.ESPHome.BluetoothScannerTest"a dead subscriber is auto-removed", a 100msassert_receiveunder full-suite CPU load); reproduced 3/3 in isolation with 0 failures, confirming it's a pre-existing timing flake in a test that only touches core ElixirRegistry(no Phoenix/PubSub/req/etc. involved) — unrelated to this bump.mise exec -- sh -c 'MIX_TARGET=host MIX_ENV=dev mix dialyzer'— passed successfully (7 pre-existing ignored findings, per.dialyzer_ignore.exs; 0 new)overview_live_test.exs,audio_live_test.exs,header_clients_test.exs,overview_fma120_test.exsand the rest of the LiveView suite are all green in the full run above.Test plan
mix format --check-formattedmix compile --warnings-as-errorsmise run test(full suite, 1607/1607)MIX_TARGET=host MIX_ENV=dev mix dialyzergit diff mix.lockscoped to exactly the 8 intended rows🤖 Generated with Claude Code