graham/prop
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(deps): document why oban_web needs override: true

Browse source 
Aligning vendoring style with the sibling towerops-web repo. They
have the same vendor/oban_pro + oban_met + oban_web setup but no
`override: true` on oban_web — because they don't have live_table.

We do (live_table requires `oban_web ~> 2.11` from hexpm), so the
override is load-bearing here. Comment captures the reason so a
future deps cleanup doesn't assume it's vestigial and remove it.
This commit is contained in:
Graham McIntire 2026-04-30 09:31:39 -05:00
parent e99bf06eb4
commit 355a9df829
No known key found for this signature in database
GPG key ID: F4ABF488E6029E59
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
mix.exs
View file

@ -91,6 +91,10 @@ defmodule Microwaveprop.MixProject do
# --unpack`) into vendor/, then commit.
{:oban_met, "~> 1.0", path: "vendor/oban_met", override: true},
{:oban_pro, "~> 1.7", path: "vendor/oban_pro"},
# Note: override: true on oban_web is required because live_table
# transitively pulls `oban_web ~> 2.11` from hexpm; without the
# override mix tries to resolve from hex and fails. towerops-web
# doesn't have live_table so it doesn't need the override.
{:oban_web, "~> 2.12", path: "vendor/oban_web", override: true},
{:credo, "~> 1.7", only: [:dev, :test], runtime: false},
{:nx, "~> 0.9", only: [:dev, :test]},