deps(mix): March 2025 dependency upgrades #2416
Conversation
| {:inflex, "2.1.0"}, | ||
| {:jason, "1.4.4", override: true}, | ||
| {:kino_live_component, "0.0.5"}, | ||
| {:logster, "1.1.1"}, | ||
| # reverted from 0.4 |
There was a problem hiding this comment.
I'd add a comment as to why but I don't remember and I don't want to revisit the trouble I had with that upgrade when I tried it a number of months ago (and forgot to document it then)
| {:phoenix_pubsub, "2.1.3"}, | ||
| {:phoenix_view, "~> 2.0"}, | ||
| {:phoenix_view, "2.0.4"}, |
There was a problem hiding this comment.
technically same as before, just with the version pinned this time
| @@ -73,7 +73,8 @@ defmodule DotCom.Mixfile do | |||
| {:address_us, "0.4.3"}, | |||
| {:aws, "1.0.4"}, | |||
| {:aws_credentials, "0.3.2", optional: true}, | |||
| {:castore, "1.0.11"}, | |||
| {:castore, "1.0.12"}, | |||
| {:cowlib, "2.14.0", override: true}, | |||
There was a problem hiding this comment.
technically not sure this override is essential, but I had a heck of a time trying to get mix to obey me with reconciling the cowboy/cowlib requirements.
There was a problem hiding this comment.
It's usually because some other dependency depends on this one at a different version number.
|
I submitted a customer support ticket in dev-blue and saw a confirmation of success logged in Splunk. And I confirmed it made it to the IRIS/HEAT dev system! |
Summary of changes
Asana Ticket: [Monthly] Upgrade Erlang, Elixir & dependencies
The second commit's a bit more involved, as it involves a major upgrade. The unit tests still pass, but I want to put it on dev-blue and test submitting the customer support form, and verify we get no surprises there.