Repository navigation
chore(init): pin the Uptide Action to v0.17.0 - #249
Merged
Merged
Conversation
Setup PRs now pin Action v0.17.0 (63e91ef). Same shape as #240: pin, pin test, golden workflows, patch changeset. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014QnPEZn2j39rjUyyRXqT5K Signed-off-by: Claude <noreply@anthropic.com>
Merged
7 tasks done
lucasbraum
added a commit
that referenced
this pull request
Oct 19, 2026
## What and why Setup PRs now pin Action v0.18.0 (`9018eb7ffc14`). Same shape as #249: pin, pin test, golden workflows, patch changeset. The only change in the goldens is the `uses:` line, in all 7 workflows. ## How it was verified **Pin checked** - `gh api repos/uptide-dev/uptide/git/ref/tags/v0.18.0`: a lightweight tag on commit `9018eb7ffc14cc382f894d53788f08e96c4e501a` (Version Packages #254). That commit is on `main`, and the GitHub release `v0.18.0` targets it (not a draft or prerelease). **Action install path at that sha** - Between v0.17.0 (`63e91ef`) and v0.18.0 (`9018eb7`), the only change in `action.yml`, `scripts/action-setup.sh`, `scripts/action-sdk.mjs`, `pnpm-lock.yaml` and `packages/cli/package.json` is the CLI's version (0.17.0 → 0.18.0). The Action's inputs, its Agent SDK install and the required `anthropic-api-key` are unchanged from what #249 verified. I did not re-run `action-setup.sh` on a clean archive this time. **Checks:** lint (2 warnings, 1 info, no errors), typecheck, `pnpm build`, onboarding tests (76 passed, 4 skipped), `actions.network.test.ts` with `UPTIDE_NETWORK=1` (6 passed), and the core suite (2407 passed, 32 skipped). I did not run the cli tests. ## Checklist - [x] Tests for the change (pin test and goldens updated) - [x] `pnpm lint && pnpm typecheck && pnpm test` pass (core only; cli not run) - [x] README and docs updated if behavior changed (n/a) - [x] Changeset added if a user would notice (`pnpm changeset`) - [x] No new dependency, or it was agreed in an issue - [x] No private code, names or paths in fixtures, tests or docs - [x] The rules in CONTRIBUTING.md ("Rules that do not bend") still hold 🤖 Generated with [Claude Code](https://claude.com/claude-code) Signed-off-by: Lucas Braum <lucasbraum@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Setup PRs now pin Action v0.17.0 (
63e91ef2a528). Same shape as #240: pin, pin test, golden workflows, patch changeset. The only change in the goldens is theuses:line, in all 7 workflows.How it was verified
Pin checked
v0.17.0is a lightweight tag on63e91ef2a52815ce5d75d3bd0fb53596956afb1c(Version Packages Version Packages #246), and the GitHub release targets that commit.uptide@0.17.0has SLSA provenance from.github/workflows/release.ymlonrefs/heads/main, source commit63e91ef2a52815ce5d75d3bd0fb53596956afb1c. The registry tarball's sha512 matches the attestation subject. I decoded the attestation payload but did not verify its Sigstore signature.Agent SDK at that sha
scripts/action-setup.shrunspnpm install --frozen-lockfile --ignore-scriptsfrom the Action's own lockfile. There,@anthropic-ai/claude-agent-sdk@0.3.296is in thepackages/cliimporter, with per-platform binaries as optional deps.scripts/action-sdk.mjsthen fails setup if the SDK or this runner's binary is missing. Since v0.16.0, the only change in the Action's install path (action.yml,action-setup.sh,action-sdk.mjs,pnpm-lock.yaml,packages/cli/package.json) is the CLI's version.action-setup.shon a cleangit archiveof 63e91ef (Node 22, linux-x64). It installed, built, printed0.17.0andAgent SDK ready: @anthropic-ai/claude-agent-sdk-linux-x64/claude.anthropic-api-key: ${{ secrets.ANTHROPIC_API_KEY }}(in every golden workflow), andaction.ymlat 63e91ef still requires it.Checks: lint (1 warning, 1 info, no errors), typecheck,
pnpm build, core tests (2329 passed, 32 skipped), andactions.network.test.tswithUPTIDE_NETWORK=1(6 passed). cli tests: 535 of 536 passed.engine-exit.test.ts› "when it runs out of memory…" timed out at 30s. It fails the same way on unmodifiedorigin/mainin the same container, so it is environmental and not this change. On the first cli run a second test also failed, but its name scrolled off and it did not recur in two later runs.Checklist
pnpm lint && pnpm typecheck && pnpm testpass (except the environmental timeout noted above)pnpm changeset)Generated by Claude Code