chore: update hex dependencies #36
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/update-hex-deps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Updates all Hex dependencies via
mix deps.update --all.Upgraded:
Also picked up the latest commit on the
aprsgit dependency (tracked onmain).Verification:
mix compile --warnings-as-errorsclean (warnings only in third-party deps error_tracker/prom_ex)mix format --check-formattedcleanmix credo --strict— no issues (2644 mods/funs)mix test— 2267/2267 passedmix dialyzer— passed successfullymix deps.audit— passed (pre-commit hook)No findings. Lockfile-only bump (6 lines); every version stays inside its
mix.exsrequirement (phoenix ~> 1.8-> 1.8.14,phoenix_live_view ~> 1.2-> 1.2.12,swoosh ~> 1.23-> 1.28.1,mox ~> 1.2-> 1.3.2,dialyxir ~> 1.0-> 1.4.8), and each bumped package's own requirements are satisfied by what is already locked (erlex 0.2.9 >= 0.2.8,idna 7.1.0 < 8.0.0,plug_crypto 2.2.0,bandit 1.12.5,nimble_ownership 1.0.2). No dep declared inmix.exsis missing from the lock.One note, not a defect: the
aprsgit dep moved to4a9adf04on upstreammain, so that code ships pinned by sha but unreviewed here. If upstream force-pushedmain, the new sha is not an ancestor of the old one and anything that lived only on the old commit silently leaves the build. A quickgit log --oneline e69c80de..4a9adf04in a clone of aprsme/aprs settles it if you care.