Skip to content

feat(stack-encrypt): run vendor KMS backends through a static keyset registry (CIP-3965) #163

feat(stack-encrypt): run vendor KMS backends through a static keyset registry (CIP-3965)

feat(stack-encrypt): run vendor KMS backends through a static keyset registry (CIP-3965) #163

Triggered via pull request October 6, 2026 11:59
Status Success
Total duration 6m 20s
Artifacts –

tests-crates.yml

on: pull_request
fmt, clippy, nextest, doctests, rustdoc
6m 11s
fmt, clippy, nextest, doctests, rustdoc
node bindings, napi typings, stack-auth-wasm
1m 58s
node bindings, napi typings, stack-auth-wasm
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
fmt, clippy, nextest, doctests, rustdoc
Error: ENOENT: no such file or directory, opendir '/home/runner/_work/stack/stack/target/tests/target'
fmt, clippy, nextest, doctests, rustdoc
ENOENT: no such file or directory, opendir '/home/runner/_work/stack/stack/target/tests/target'
stack-encrypt cannot be published
stack-encrypt has a git dependency, so cargo cannot package it. The dry run skips it until that dependency is on crates.io.
stack-kms cannot be published
stack-kms has a git dependency, so cargo cannot package it. The dry run skips it until that dependency is on crates.io.