Skip to content

Commit c35cab2

Browse files
owineclaude
andcommitted
fix: detect critical stacks only for existing stacks, not new ones
New stacks don't have compose files on the remote server yet, causing "Compose file not found" warnings during critical stack detection. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent c900faf commit c35cab2

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

.github/workflows/deploy.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -596,10 +596,10 @@ jobs:
596596
597597
- name: Detect critical stacks
598598
id: detect-critical
599-
if: steps.backup.outputs.deployment_needed == 'true' && inputs.auto-detect-critical == true
599+
if: steps.backup.outputs.deployment_needed == 'true' && inputs.auto-detect-critical == true && steps.detect-changes.outputs.has_existing_stacks == 'true'
600600
run: |
601601
./.compose-workflow/scripts/deployment/detect-critical-stacks.sh \
602-
--stacks "${{ join(fromJSON(steps.discover-stacks.outputs.stacks), ' ') }}" \
602+
--stacks "${{ join(fromJSON(steps.detect-changes.outputs.existing_stacks), ' ') }}" \
603603
--ssh-user "${{ secrets.SSH_USER }}" \
604604
--ssh-host "${{ secrets.SSH_HOST }}"
605605

0 commit comments

Comments
 (0)