GitHub release action for #C084HP11VPF https://github.com/nf-core/proteinannotator/actions/runs/25508985601/job/74863765510 fails to trigger a proper AWS full_test run in https://cloud.seqera.io/orgs/nf-core/workspaces/AWSmegatests/watch Any idea why?

You've got Claude, right? 😉

⏺ The job failed because the awsfulltest.yml workflow has an unrendered Jinja2 template tag leaking into the action inputs.
  Line 23 of .github/workflows/awsfulltest.yml reads:

  echo "revision={%- raw -%}${{ (github.event_name == 'workflow_dispatch' || ...) && github.sha || 'dev' }}" >>
  "$GITHUB_OUTPUT"

  The {%- raw -%} should have been stripped by nf-core pipelines sync when the template was rendered, but it got committed
  verbatim (likely the matching {%- endraw -%} was lost or the raw block was malformed in the source template). At runtime
  the literal text {%- raw -%} is prepended to the SHA, so the revision output becomes:

  {%- raw -%}cbf78d471f62d91af666e8c77bcd580b4743c6be

  That bad value then propagates into the seqeralabs/action-tower-launch inputs, which you can see in the log:
  - revision: {%- raw -%}cbf78d471f... (no such git ref → Tower launch fails)
  - workdir: s3://.../work-{%- raw -%}cbf78d471f...
  - outdir: s3://.../results-{%- raw -%}cbf78d471f...

  Fix: edit that line to drop the stray {%- raw -%} (and find/restore the matching {%- endraw -%} if it was meant to wrap a
  block). Easiest approach is to replace the file with the current nf-core template version:

  # from a clean clone
  echo 'revision=${{ (github.event_name == '\''workflow_dispatch'\'' || github.event_name == '\''release'\'') && github.sha
  || '\''dev'\'' }}' >> "$GITHUB_OUTPUT"

  or just re-sync from nf-core/tools so the template renders correctly.

aw thanks, it's usually something else..let me try this 😛

Tbh yes, probably. You could muck about with re-tagging and re-releasing but it would be more trouble than it's worth. I'll approve the PRs to help you get it through quick

alrightyy, thanks!

nf-core pro-move: a branch called

patch

should be able to push directly to

main

for these kind of things

TIL

I treid

patch-aws-test-config

and didnt work, should it be

patch:aws-test-config

?

i think so

let me try

tagged you both, thanks 😄

shakefist this should have been triggered on the original reviews before the merge to master/main to avoid this

not sure how I missed this...have done 3 template merges so far..probably thats why 😛