docs: app-baseline-kit dependency patterns across the fleet - #2206
Conversation
Add docs/guides/BASELINE_KIT_DEPENDENCY.md as the catalog of accepted patterns for the shared app-baseline-kit dependency, plus a one-line link from the INTEGRATION_GUIDE monorepo-dependency callout. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Workflow source neededPR #2206 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely. Please do one of:
Once a valid source is present, this warning will not be reposted. |
|
Gate fast-pass: docs-only change detected; heavy checks skipped. |
Automated Status SummaryHead SHA: 5832745
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeNo scope information available Tasks
Acceptance criteria
|
There was a problem hiding this comment.
Pull request overview
Adds a new documentation guide that defines accepted app-baseline-kit dependency patterns for consumer repos and links it from the integration guide.
Changes:
- Adds
docs/guides/BASELINE_KIT_DEPENDENCY.mdwith Pattern A/B/C/vendoring guidance and migration steps. - Adds an
INTEGRATION_GUIDE.mdcross-reference to the new dependency-pattern catalog. - Documents per-repo pattern mapping and decision order for future consumers.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
docs/INTEGRATION_GUIDE.md |
Adds a link from the monorepo dependency callout to the new guide. |
docs/guides/BASELINE_KIT_DEPENDENCY.md |
New reference catalog for app-baseline-kit dependency declaration patterns. |
| @@ -0,0 +1,203 @@ | |||
| # Declaring the `app-baseline-kit` Dependency | |||
| - **Pattern C (frozen SHA) is deprecated.** A `pyproject.toml` that pins | ||
| `app-baseline-kit @ git+...@<sha>#...` is a stopgap, not a target state. Any | ||
| repo on Pattern C must migrate to Pattern A (it tracks Workflows `main` and | ||
| removes the SHA from the loop). See [Fixing a Pattern C repo](#fixing-a-pattern-c-repo-frozen-sha--pattern-a). |
| > Exclude it from `requirements.lock` with `[tool.uv.pip] no-emit-package` so a | ||
| > frozen SHA in the lock cannot conflict with the unpinned `@main` URL when | ||
| > Workflows `main` advances. See | ||
| > [Monorepo Package Dependencies](ops/CONSUMER_REPO_MAINTENANCE.md#monorepo-package-dependencies-app-baseline-kit). | ||
| > [Monorepo Package Dependencies](ops/CONSUMER_REPO_MAINTENANCE.md#monorepo-package-dependencies-app-baseline-kit), | ||
| > and [Declaring the `app-baseline-kit` Dependency](guides/BASELINE_KIT_DEPENDENCY.md) | ||
| > for the catalog of accepted patterns and how to choose one. |
Summary
Adds
docs/guides/BASELINE_KIT_DEPENDENCY.md— the catalog of accepted patterns for pulling in the sharedapp-baseline-kitpackage (thebaseline_kitimport) acrossstranske/*consumer repos.The guide documents:
@maininpyproject.toml+[tool.uv.pip] no-emit-package, with thePension-Datalock-SHA variant.requirements-baseline.txtfor custom build backends (TPP).pyproject.toml— deprecated, with step-by-step migration to Pattern A.Inv-Man-Intake).It complements the operational walkthrough in
ops/CONSUMER_REPO_MAINTENANCE.md → Monorepo Package Dependencies(the conflict mechanics and no-emit fix) — that doc is for debugging install failures; this guide is for choosing a pattern.Also
INTEGRATION_GUIDE.mdmonorepo-dependency callout to the new pattern catalog.🤖 Generated with Claude Code