Commit 8d02fd4
committed
ogar-from-{ruff,rails}: rev-pin ruff to 61ce2b49 (codex P1 on #149)
ogar-from-ruff reads ruff_spo_triplet::Model::inherits (added in ruff #40).
With no committed Cargo.lock, the floating `branch = "main"` pin could
resolve to a ruff rev WITHOUT that field on a clean build and fail to
compile — and the prior commit's '61ce2b49' claim didn't travel. Pin all
three ruff refs (ruff_spo_triplet + ruff_spo_address in ogar-from-ruff,
ruff_ruby_spo in ogar-from-rails) to the exact rev 61ce2b49 (ruff main at
the #40 merge). Same rev across both crates: they share ruff_spo_triplet
internally, so a mismatch would double-check-out ruff.
Verified: ruff re-locks to 61ce2b49; ogar-from-ruff 48 tests + ogar-from-rails
green; workspace check + clippy -D warnings clean.1 parent 1db31bc commit 8d02fd4
2 files changed
Lines changed: 12 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
22 | | - | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
23 | 25 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
18 | | - | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
19 | 26 | | |
0 commit comments