Close issue-core package blocker
This commit is contained in:
6
SCOPE.md
6
SCOPE.md
@@ -133,9 +133,9 @@ lessons into reusable S5 app release patterns.
|
||||
docs directly when app releases consume forge artifacts.
|
||||
- The final source-of-truth decision for forge ownership is recorded in
|
||||
`docs/forge-source-of-truth-decision.md`.
|
||||
- The `issue-core` migration is still blocked on publishing `issue-core==0.2.0`
|
||||
with package credentials in the `issue-core` repo and refreshing the
|
||||
`vergabe-teilnahme` lock in its source repo.
|
||||
- The `issue-core` migration blocker is closed: `issue-core==0.2.0` is
|
||||
published to the Gitea PyPI registry, and the `vergabe-teilnahme` lock in its
|
||||
source repo resolves it from the registry rather than a sibling checkout.
|
||||
- `vergabe-teilnahme` is represented as a local Helm chart plus values,
|
||||
ingress, Makefile targets, and an operator runbook.
|
||||
- Reusable S5 app onboarding, app data restore handoff, and manifest
|
||||
|
||||
Reference in New Issue
Block a user