veza/veza-backend-api/internal/api/handlers
senke dbda03f45d
Some checks failed
Backend API CI / test-unit (push) Waiting to run
Backend API CI / test-integration (push) Waiting to run
Veza CI / Backend (Go) (push) Waiting to run
Veza CI / Frontend (Web) (push) Waiting to run
Veza CI / Notify on failure (push) Blocked by required conditions
Veza CI / Rust (Stream Server) (push) Has been cancelled
Security Scan / Secret Scanning (gitleaks) (push) Has been cancelled
ci(cache): add save-always to persist cache on job failure
By default actions/cache@v4 only saves the cache when the job completes
successfully. Runs 71 / 74 failed at the Lint / Install Go tools step
before reaching the post-step cache upload, so the Go tool binaries
cache (govulncheck + golangci-lint) was never persisted and every
subsequent run paid the ~3 min "go install @latest" cost again.

Add `save-always: true` to:
  - Cache Go tool binaries (ci.yml)
  - Cache rustup toolchain (ci.yml)
  - Cache Cargo deps and target (ci.yml)
  - Cache govulncheck binary (backend-ci.yml)

so the next run benefits from whatever the previous job managed to
install, even if a downstream step later fails.
2026-04-14 18:01:40 +02:00
..
chat_handlers.go ci: bump Go to 1.25 and fix goimports drift in 3 files 2026-04-14 17:02:09 +02:00
rbac_handlers.go [T0-006] test(backend): Amélioration couverture tests Go - Scripts et tests RBAC 2026-01-04 01:44:21 +01:00
rbac_handlers_test.go incus deployement fully implemented, Makefile updated and make fmt ran 2026-01-13 19:47:57 +01:00