Skip to content

Commit cf5b39e

Browse files
jeffreyavenclaude
andcommitted
Remove redundant unconditional setup-stackql step
stackql-assert ran setup-stackql on every invocation and then called stackql-exec, which already performs a guarded, reuse-if-present install. The extra setup step re-downloaded the binary each time, and when it ran after a workflow flipped the releases "latest" pointer it could 404. Drop the redundant step; setup is handled by stackql-exec. The Check Results step needs no stackql binary. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent 61a59c1 commit cf5b39e

1 file changed

Lines changed: 3 additions & 5 deletions

File tree

action.yml

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -33,11 +33,9 @@ inputs:
3333
runs:
3434
using: "composite"
3535
steps:
36-
- name: Setup StackQL
37-
uses: stackql/setup-stackql@v2
38-
with:
39-
use_wrapper: true
40-
36+
# No setup-stackql here: stackql-exec (invoked below) performs a guarded
37+
# install that reuses an existing binary if one is already on PATH. Running
38+
# setup-stackql again here would re-download unconditionally.
4139
- name: Execute StackQL Command
4240
id: exec-query
4341
uses: stackql/stackql-exec@v2

0 commit comments

Comments
 (0)