PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m16s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 10s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s
PR Check / AI code review (opencode) (pull_request) Successful in 41s
Build Dockerfile on every v* tag push (created by release-please when the release PR merges) and push registry.noelsabia.dev/cv_website/nuxt as the version, sha-<12> and latest. Main pushes do not build: the registry holds releases, not commits. The job runs in node:22-bookworm and needs only the Docker client, so the act_runner must expose its host socket (container.docker_host: automount); a preflight step fails with that cause when it does not.
1.7 KiB
1.7 KiB
Decisions
- PR pipeline layering - What runs pre-commit, what runs in Gitea Actions, what the AI review does, and the cost rule that decides.
- AI review setup - Plan model, env-only auth against prompt injection, read-only agent, and the verdict line as the posting gate.
- Vulnerability audit policy - Blocking audit, reviewed ignore-list for unfixable advisories, and the pnpm-11 settings home.
- Release engineering - release-please in manifest mode, conventional commits as input, message format enforced at commit time.
- Snyk paused and secrets policy - Why the job is skipped rather than deleted, and the token scopes every workflow secret needs.
- Publishing images to the own registry - A release tag builds and pushes to registry.noelsabia.dev; main pushes do not build.
- Dev container shape - The source is bind-mounted into a container that already holds the dependencies, and the dev server runs as the image's
nodeuser. - Build layer order - Why the manifests are copied before the source, and what invalidates what.
- Build context filter - What
.dockerignoremay exclude, and the one thing it must never exclude. - Production image shape - Multi-stage, digest-pinned, non-root runnable Node server; measured build and serve.
- Repository and compose layout - The Dockerfiles live with the app; the stack is assembled in
Local_Development. - Mockup layout - One
DESIGN.mdper screen, with the screenshot and the source embedded.