Elijah/newdrive
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Harden CI and switch release builds to tagged immutable images
All checks were successful
CI / Backend (push) Successful in 29s
Details
CI / Frontend (push) Successful in 9m27s
Details
CI / Contracts and repository policy (push) Successful in 7s
Details
CI / Container (push) Successful in 18s
Details

Browse source
This commit is contained in:
Elijah 2026-07-15 19:21:07 -07:00
parent bed2e6cfb6
commit f24e96efa7
60 changed files with 4710 additions and 64 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/dependencies.md Normal file
View file

@ -0,0 +1,14 @@
# Dependency policy
Dependencies are pinned in `go.mod`, `web/package.json`, the npm lockfile, container tags, and CI workflow references. Add a runtime dependency only when its functionality is actively used, and record architectural additions in an ADR before merging.
## Phase 0 baseline
Backend production code currently uses the Go standard library. Chi, pgx, sqlc, and the migration runner are approved by the architecture baseline and will be pinned when their first Phase 1 implementation is added.
Frontend runtime dependencies are React, React DOM, TanStack Query, and TanStack Router. Development dependencies provide TypeScript, Vite, Vitest, ESLint, React tooling, and type declarations.
Container baselines are Go 1.26 on Debian Bookworm, Node 24 on Debian Bookworm, PostgreSQL 18.4 on Debian Bookworm, and a Debian Bookworm slim runtime. Production deployment should pin tested image digests as part of its release configuration.
Dependency updates must pass the full repository check and production image build. Avoid packages that duplicate standard-library functionality or introduce background network behavior, telemetry, install scripts, or unreviewed native binaries.