Skip to content

fix: bump tw CLI to v0.31.0 across all workflows#78

Merged
adamrtalbot merged 1 commit into
mainfrom
fix/update-tw-cli-to-v0.31.0
May 13, 2026
Merged

fix: bump tw CLI to v0.31.0 across all workflows#78
adamrtalbot merged 1 commit into
mainfrom
fix/update-tw-cli-to-v0.31.0

Conversation

@adamrtalbot
Copy link
Copy Markdown
Contributor

Summary

  • Bumps the tw CLI download in every workflow to v0.31.0.
  • Aligns seqera-showcase-production.yml (was v0.29.1) and the other five workflow files (still on v0.15.0) onto a single version.

Why

The staging run 25724525353 failed in the finish workflow step with:

tw -o json runs dump -id k4MvMy4IBS51a -o tmp.k4MvMy4IBS51a.tar.gz -w 14715071736572
…
ERROR: Unexpected error while processing request - Error ID: 2N5X56V80d5z6aAwO7OiWL

v0.15.0 (mid-2024) predates tower-cli#520 (Jun 2025) — "fix: nullpointerexception when running runs dump for a nextflow -with-tower run" — which handles null launch fields in JSON output and catches exceptions while downloading workflow logs. The runs in this pipeline are launched via tw launch (-with-tower), which is exactly the path that fix addresses.

The CLI flag layout (-o json runs dump -id … -o … -w …) is unchanged between v0.15.0 and v0.31.0, so no Python changes are needed.

Test plan

  • Trigger seqera-showcase-autotest-staging via workflow_dispatch and confirm the clearup-and-delete job's finish workflow step succeeds end-to-end (runs dump + Slack post + delete).
  • Confirm tower check step prints Tower CLI version 0.31.0 in both jobs.

v0.15.0 predates tower-cli#520 (Jun 2025), which fixes a
NullPointerException in `runs dump` for nextflow `-with-tower`
launches. Align production (v0.29.1) and the remaining workflows
(v0.15.0) on v0.31.0 to unblock the clearup-and-delete job that
currently fails with "Unexpected error while processing request"
during the dump step.

Generated by Claude Code
@adamrtalbot adamrtalbot deployed to delay1mins May 13, 2026 13:37 — with GitHub Actions Active
@adamrtalbot adamrtalbot merged commit 1e11ea2 into main May 13, 2026
3 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant