Skip to content

Tags

Tags

v2.5.1

Toggle v2.5.1's commit message
Move to github-script v9, checkout v7 and setup-node v7

- actions/github-script v9 in action.yml and the test workflow
- actions/checkout v7 and actions/setup-node v7 with check-latest in CI
  (October 2026 Node.js security releases)
- CONTRIBUTING: Node.js 24.22.1 or later

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

v2

Toggle v2's commit message
Move to github-script v9, checkout v7 and setup-node v7

- actions/github-script v9 in action.yml and the test workflow
- actions/checkout v7 and actions/setup-node v7 with check-latest in CI
  (October 2026 Node.js security releases)
- CONTRIBUTING: Node.js 24.22.1 or later

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

v2.5.0

Toggle v2.5.0's commit message
added win arm64

v2.4.0

Toggle v2.4.0's commit message
Scope auth and command to step outputs, not GITHUB_ENV

setupAuth and getStackqlCommand previously wrote AUTH and STACKQL_COMMAND
via core.exportVariable, which persists through GITHUB_ENV to every later
step in a job. That let auth/args from one action invocation carry into the
next (e.g. github bearer auth being applied to a later cloudflare query).

Emit both as step outputs (core.setOutput) and wire them through action.yml
via steps.<id>.outputs, so they are scoped to this invocation and cannot
leak across steps or actions. Tests updated to the setOutput contract with
added setupAuth coverage.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

v2.3.1

Toggle v2.3.1's commit message
use latest setup-stackql

v2.3.0

Toggle v2.3.0's commit message
updated action versions

v2.2.3

Toggle v2.2.3's commit message
tests updates

v2.2.2

Toggle v2.2.2's commit message
name change

v2.2.1

Toggle v2.2.1's commit message
updated setup-stackql

v2.2.0

Toggle v2.2.0's commit message
updated setup-stackql version