@@ -66,6 +66,16 @@ updates:
6666 # found" on a log page nobody visits, and the symptom is simply that no PR
6767 # ever arrives. The e2e test asserts this path holds a Cargo.toml.
6868 directory : /languages/typescript/packages/protect-ffi
69+ # Lockfile only, like the EQL entry below and for the same reason: this
70+ # workspace depends by path on eql-bindings, a member of the EQL
71+ # workspace. A requirement this entry raised could be written into
72+ # packages/eql/crates/eql-bindings/Cargo.toml without the EQL Cargo.lock,
73+ # the #1205 shape one edge over. An update that needs a manifest change,
74+ # in this workspace or that one, is dropped and made by hand. This applies
75+ # to Dependabot security updates too; osv-scanner still reports the
76+ # advisory. Held by
77+ # scripts/__tests__/dependabot-cargo-cross-workspace.test.mjs.
78+ versioning-strategy : lockfile-only
6979 # Monthly, where npm and actions are weekly. The deviation is about
7080 # validation cost, not risk appetite: a Cargo.lock bump is checked by
7181 # tests-rust.yml — one Blacksmith job, 45-minute timeout, cargo test +
@@ -138,23 +148,39 @@ updates:
138148 - version-update:semver-major
139149
140150 # ── Cargo (packages/eql — the second Rust workspace) ───────────
141- # The EQL subtree brought a second Cargo workspace: five members
142- # (crates/eql-{domains,codegen,tests-macros,bindings} plus tests/sqlx) and
143- # its own Cargo.lock. It needs its own entry because Dependabot's cargo
144- # `directory:` is a single workspace root, not a glob — the protect-ffi entry
145- # above cannot reach it. The lockfile-to-ecosystem check in
146- # e2e/tests/supply-chain.e2e.test.ts asserts coverage per ECOSYSTEM, so it
147- # was already satisfied by that entry and would NOT have caught this gap;
148- # the symptom would simply have been that no PR ever arrived.
151+ # The EQL subtree brought a second Cargo workspace: six members
152+ # (crates/eql-{domains,codegen,tests-macros,bindings}, tests/sqlx and
153+ # tests/encryption) and its own Cargo.lock. It needs its own entry because
154+ # Dependabot's cargo `directory:` is a single workspace root, not a glob —
155+ # the protect-ffi entry above cannot reach it. The lockfile-to-ecosystem
156+ # check in e2e/tests/supply-chain.e2e.test.ts asserts coverage per
157+ # ECOSYSTEM, so it was already satisfied by that entry and would NOT have
158+ # caught this gap; the symptom would simply have been that no PR ever
159+ # arrived.
149160 - package-ecosystem : cargo
150161 # The workspace root, where Cargo.toml and Cargo.lock live. Not `/`, and
151162 # not a crate directory — same trap as the protect-ffi entry documents.
152163 directory : /packages/eql
164+ # Lockfile only: this entry must never edit a manifest. The workspace
165+ # depends by path on root-workspace crates (see the ignores below), so a
166+ # requirement it would raise can live in the ROOT Cargo.toml, outside this
167+ # workspace; editing it there without the root Cargo.lock broke every root
168+ # `--locked` build (#1205, #1207). An update that needs a manifest change is
169+ # dropped rather than proposed, and is made by hand.
170+ #
171+ # That includes Dependabot SECURITY updates: `versioning-strategy` governs
172+ # them as well as version updates, so a security fix that needs a
173+ # requirement raised gets no PR from this entry. osv-scanner still reports
174+ # the advisory (it reaches this lockfile with `--recursive ./`), and the fix
175+ # is made by hand. Held, with the other two cargo entries, by
176+ # scripts/__tests__/dependabot-cargo-cross-workspace.test.mjs.
177+ versioning-strategy : lockfile-only
153178 # Monthly, matching protect-ffi and for the same reason: validating a
154179 # Cargo.lock bump here means the sharded SQLx matrix in test-eql.yml, which
155180 # compiles the full dependency tree and runs against live Postgres with
156- # CipherStash credentials. Security fixes are unaffected — those are driven
157- # by alerts, not by `schedule`.
181+ # CipherStash credentials. The schedule does not delay security fixes —
182+ # those are driven by alerts, not by `schedule` — though `lockfile-only`
183+ # above still drops one that needs a manifest edit.
158184 #
159185 # No `day:`, for the reason recorded above: it applies to `interval: weekly`
160186 # and would be configuration that does nothing.
@@ -195,6 +221,26 @@ updates:
195221 # a registry version for a crate we release here would fight the lockstep
196222 # version hook (scripts/sync-lockstep-versions.mjs).
197223 - dependency-name : " eql-bindings"
224+ # Inherited from the ROOT workspace. tests/encryption depends by path on
225+ # packages/stack-kms and packages/stack-encrypt, and eql-bindings on
226+ # stack-encrypt behind its optional `stack-encrypt` feature. Those crates
227+ # declare these `{ workspace = true }`, so their requirements come from
228+ # the root Cargo.toml even when built here. The root entry below ignores
229+ # them because they move by hand with cipherstash-suite: the root
230+ # manifest pins recipher and cllw-ore with `=`, and so does the Go guest.
231+ # Without these lines this entry bumped them in this lockfile and, to
232+ # satisfy the exact pins, rewrote the root Cargo.toml without touching
233+ # the root Cargo.lock or the guest's pin, breaking every root `--locked`
234+ # build and the guest (#1205, #1207). vitaminc* also keeps eql-bindings
235+ # on the line stack-encrypt and the guest build against.
236+ # versioning-strategy above already stops the manifest edit; these keep
237+ # the lockfile from moving these crates apart from the root's.
238+ # scripts/__tests__/dependabot-eql-inherited-ignores.test.mjs fails when
239+ # the root entry ignores a crate this entry does not.
240+ - dependency-name : " recipher"
241+ - dependency-name : " cllw-ore"
242+ - dependency-name : " zerokms-protocol"
243+ - dependency-name : " vitaminc*"
198244 # Major bumps are reviewed and applied manually, not by Dependabot.
199245 - dependency-name : " *"
200246 update-types :
@@ -213,6 +259,17 @@ updates:
213259 - /packages/stack-encrypt/fuzz
214260 - /languages/golang/encrypt/guest
215261 - /languages/golang/auth/guest
262+ # Lockfile only, like the other two cargo entries. Every one of these
263+ # workspaces shares crates by path with another: the fuzz crates and both
264+ # guests depend on root-workspace crates, the encrypt guest also on
265+ # eql-bindings, and the EQL workspace on stack-encrypt and stack-kms. Those
266+ # root crates take `{ workspace = true }` requirements from the root
267+ # Cargo.toml, so a manifest edit made for any one of these lockfiles can
268+ # leave the others stale under `--locked`. An update that needs a manifest
269+ # change, security updates included, is dropped and made by hand; osv-scanner
270+ # still reports the advisory. Held by
271+ # scripts/__tests__/dependabot-cargo-cross-workspace.test.mjs.
272+ versioning-strategy : lockfile-only
216273 # Monthly, matching the other two cargo entries.
217274 schedule :
218275 interval : monthly
0 commit comments