You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test-php failed on main in run 25015144215 (commit da7ce0e) with ##[error]unable to get latest version from go-task/setup-task@v1. The same error broke build-web and test-prqlc-c in the prior main run 25007961050 — so this is a recurring failure mode, not a one-off.
Root cause: the action defaults to version: 3.x and resolves the concrete release via https://api.github.com/repos/go-task/task/releases?per_page=100. When that response is empty (rate limit, transient API hiccup), installer.ts throws unable to get latest version. max-retries: 3 only re-tries the HTTP call, not the empty-result branch.
Solution
Pin version: 3.50.0 (the current latest task release, published 2026-04-13) at every go-task/setup-task@v1 call site. The action's computeVersion short-circuits when semver.valid(version) is true, skipping the API lookup entirely — so a concrete semver eliminates the failure mode.
Updated four sites:
.github/workflows/test-php.yaml
.github/workflows/build-web.yaml
.github/workflows/test-prqlc-c.yaml
.github/actions/tend-setup/action.yaml (also covers tend-* workflows that consume this composite action)
The commented-out reference in .github/workflows/tests.yaml:293 was left untouched.
Testing
Can only be verified end-to-end by CI. The change is mechanical — a value pinned in YAML — and matches the action's documented behavior.
The default `version: 3.x` makes `go-task/setup-task@v1` resolve the
latest tag via the GitHub releases API. That call has failed twice in
the last few hours on main with `unable to get latest version`,
breaking test-php (run 25015144215) and build-web/test-prqlc-c
(run 25007961050). Pinning a concrete semver makes the action skip
the API call entirely (`semver.valid(version)` short-circuits in
the action's installer.ts).
Co-Authored-By: Claude <noreply@anthropic.com>
Opened #5840 to add the bump to running-tend's weekly section. Note that workflows.weekly is currently disabled in .config/tend.toml, so the task is defined but won't actually run until weekly is re-enabled — flagged that in the PR description.
Note that workflows.weekly is currently disabled in .config/tend.toml, so the task is defined but won't actually run until weekly is re-enabled — flagged that in the PR description.
Historical artifact. The setting was added in #5727 when the workflow was named renovate and only auto-opened dependency-update PRs — the comment "Dependabot already handles dependency updates" still describes that scope. #5760 regenerated the tend workflows and renamed [workflows.renovate] → [workflows.weekly], but the enabled = false and its comment carried over verbatim without revisiting whether the original justification still applied.
The renamed weekly skill does more than the old renovate one: it (1) reviews open dependency PRs and approves safe ones (patch/minor with green CI), and (2) runs any repo-specific weekly tasks defined in running-tend — which now includes the go-task pin bump from #5840. Neither of those overlaps with what Dependabot itself does, so re-enabling looks safe.
Happy to open a follow-up PR flipping enabled = true and removing the stale comment if you'd like.
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
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.
Problem
test-phpfailed on main in run 25015144215 (commit da7ce0e) with##[error]unable to get latest versionfromgo-task/setup-task@v1. The same error brokebuild-webandtest-prqlc-cin the prior main run 25007961050 — so this is a recurring failure mode, not a one-off.Root cause: the action defaults to
version: 3.xand resolves the concrete release viahttps://api.github.com/repos/go-task/task/releases?per_page=100. When that response is empty (rate limit, transient API hiccup),installer.tsthrowsunable to get latest version.max-retries: 3only re-tries the HTTP call, not the empty-result branch.Solution
Pin
version: 3.50.0(the current latest task release, published 2026-04-13) at everygo-task/setup-task@v1call site. The action'scomputeVersionshort-circuits whensemver.valid(version)is true, skipping the API lookup entirely — so a concrete semver eliminates the failure mode.Updated four sites:
.github/workflows/test-php.yaml.github/workflows/build-web.yaml.github/workflows/test-prqlc-c.yaml.github/actions/tend-setup/action.yaml(also covers tend-* workflows that consume this composite action)The commented-out reference in
.github/workflows/tests.yaml:293was left untouched.Testing
Can only be verified end-to-end by CI. The change is mechanical — a value pinned in YAML — and matches the action's documented behavior.
Automated fix for failed run 25015144215.