GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Tags · stackql/stackql-exec
Tags
v2.5.1Move 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 <[email protected]> v2Move 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 <[email protected]> v2.4.0Scope 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) <[email protected]> PreviousNext
|
| You are visitor 01402520 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |