From 355a9df829424173aa91795a87de2c251625bd34 Mon Sep 17 00:00:00 2001 From: Graham McIntire Date: Thu, 30 Apr 2026 09:31:39 -0500 Subject: [PATCH] chore(deps): document why oban_web needs override: true MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- mix.exs | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/mix.exs b/mix.exs index b0a785db..390fb6d3 100644 --- a/mix.exs +++ b/mix.exs @@ -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]},