8715411727
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
The foundary cookbook was using template: "default" which seeds a flat CI pipeline without the COMPONENT_STEPS_BELOW marker. When components were added via batch API, updateWoodpeckerYml couldn't find the marker and silently returned the file unchanged — component build/deploy steps were never inserted. This caused component images to never be built, leaving pods at 0 replicas indefinitely. The skeleton template has the correct DAG-mode pipeline with markers for component step insertion and build-complete dependency wiring. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| aeries-1-genesis.yaml | ||
| aeries-2-simulation.yaml | ||
| aeries-3-society.yaml | ||
| composable-app.yaml | ||
| evolving-app.yaml | ||
| foundary.yaml | ||
| full-stack-feature.yaml | ||
| landing-page.yaml | ||
| sdlc-flow.yaml | ||
| slackpath-1-authenticated-service.yaml | ||
| slackpath-2-async-worker-pipeline.yaml | ||
| slackpath-3-realtime-chat.yaml | ||
| slackpath-4-microservice-constellation.yaml | ||
| slackpath-5-full-lifecycle.yaml | ||