The previous layout placed epic folders directly under docs/work/
alongside prds/ and _system/. Tightening: epics now live in their
own docs/work/epics/ subfolder, peer to prds/ and _system/. Same
shape as the existing prds/ bucket.
Final docs/work/ layout:
README.md
prds/<slug>.prd.md
_system/_state.json
epics/<slug>/_epic.md + <story-folder>/_story.md
Renames (git mv preserves history):
- docs/work/binder-wrap-helper/
-> docs/work/epics/binder-wrap-helper/
- docs/work/library-evaluation-policy/
-> docs/work/epics/library-evaluation-policy/
- docs/work/ci-security-and-supply-chain/
-> docs/work/epics/ci-security-and-supply-chain/
Tooling updates:
- state-builder.mjs walks workRoot/epics/ directly; SKIP_FOLDERS
obsoleted (no more sibling folders to filter out).
- dispatch.mjs's findNextTask, tickStoryBulletInEpic, and
flipEpicDoneIfAllStoriesDone all join with "epics" segment.
- prd-ship.mjs's deriveShippingCommits walks workRoot/epics/ and
git-logs docs/work/epics/<epic>/.
- decomposer.prompt.md emits epics under docs/work/epics/<epic-id>/.
- handoff + grill-with-docs glossary references updated.
- Glossary entry for Epic updated.
Reserved future shape: when a task-tracker integration (ClickUp,
Linear) ships, the epics/ subfolder hosts <task-id>-<slug>/
folders. Today it just hosts bare slugs.
2.7 KiB
2.7 KiB
id, epic, title, type, status, feature, depends-on, blocks, created, updated
| id | epic | title | type | status | feature | depends-on | blocks | created | updated | |
|---|---|---|---|---|---|---|---|---|---|---|
| 03-renovate-adoption | ci-security-and-supply-chain | Renovate adoption | technical-story | done | tooling |
|
2026-05-14T18:59:12+02:00 | 2026-05-14T19:21:52.308Z |
Goal
Ship .github/renovate.json configuring automated dependency management: grouped per-ecosystem npm bumps, Dockerfile base-image tracking, GitHub Actions SHA pinning, automerge for green minor+patch PRs, and a single dependency dashboard issue.
Why
Major-tag pinning for GitHub Actions is documented insecure — the 2025 tj-actions/changed-files incident proved it. Renovate's pinGitHubActionDigests preset automates the one-time SHA-pin sweep and keeps SHAs current thereafter. Grouping ecosystem clusters (Sentry, OTel, tRPC, Payload, Inversify) into weekly PRs prevents noise while ensuring drift is surfaced. Automerge on green minor+patch PRs removes human toil for routine bumps.
Done when
.github/renovate.jsonexists and is valid JSON, extending presets:config:base,helpers:pinGitHubActionDigests,:separateMajorReleases,:automergeMinor,:automergePatch.packageRulesgroups@sentry/*,@opentelemetry/*,@trpc/*,payload*, andinversify*into per-cluster weekly PRs.- Dockerfile manager is enabled for
.sandcastle/Dockerfile. dependencyDashboard: trueis set (opens a single Renovate-managed issue summarising open + queued PRs, labeledrenovate/dashboardper PRD Q6).- Renovate's bump commits use
chore(deps):(minor/patch) andchore(deps-major):(major) commit-message prefixes so release-please's per-package bump rules apply cleanly. pnpm typecheck && pnpm lint && pnpm test && pnpm conformance && pnpm fallow:audit && pnpm coverage:diffall pass (no executable code change; JSON config only).
In scope
.github/renovate.json— full Renovate configuration.
Out of scope
- Verifying the first Renovate PR (SHA-pin sweep) — that happens when the GitHub App runs, not at commit time. The success criterion (all
@v<N>pins rewritten to SHAs) is verified when Renovate's first PR merges. - Renovate Dependency Dashboard →
docs/work/task integration — explicitly out of scope in the PRD.
Tasks
- Create
.github/renovate.jsonextending presetsconfig:base,helpers:pinGitHubActionDigests,:separateMajorReleases,:automergeMinor,:automergePatch; addpackageRulesgrouping@sentry/*,@opentelemetry/*,@trpc/*,payload*,inversify*into weekly per-cluster PRs; enable Dockerfile manager for.sandcastle/Dockerfile; setdependencyDashboard: true; setcommitMessagePrefixto enforcechore(deps):/chore(deps-major):per Conventional Commits; one commit, all gates pass.