You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit de14775
Browse filesBrowse the repository at this point in the historyBrowse files
feat(eql)!: build eql-bindings' stack-encrypt feature on vitaminc ADR 0001 so the EQL jobs and the EQL guest stay green
eql-bindings' `stack-encrypt` feature and tests/encryption compile
stack-encrypt by path, so they move with it.
- The EQL workspace carries the same temporary vitaminc pin as the root,
the fuzz crate and both guests: every workspace that compiles
stack-encrypt now resolves one vitaminc.
- `encryption::targets` and the generated `v3::targets` take `FfiValue`
and `ValueKind` from `stack_encrypt::dynamic` (the feature turns on
stack-encrypt's `dynamic`); the generator emits the new import.
`vitaminc-aead-value` is gone from both manifests.
- The `Ciphertext` target takes `Plaintext` in place of `Encrypt` and
`Decrypt + Send + 'static` in place of `Decrypt<'static>`.
- The encrypt guest's lockfile drops `vitaminc-aead-value`, which only
its `eql` build still pulled in.
No other EQL code names a vitaminc API.
0 commit comments