Skip to content

Back-merge the 4.0.3 security patch into dev - #168

Open
mashehu wants to merge 3 commits into
devfrom
backmerge-security-patch-4.0.3
Open

Back-merge the 4.0.3 security patch into dev#168
mashehu wants to merge 3 commits into
devfrom
backmerge-security-patch-4.0.3

Conversation

@mashehu

@mashehu mashehu commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Forward-ports the merged master security patch into dev so the fix is a shared ancestor and the coming removal of the momentarily ignored lint tests (coming with nf-core/tools 4.1.0) propagates cleanly.

nf-core-bot and others added 3 commits July 28, 2026 14:18
This pipeline's TEMPLATE branch never received the nf-core/tools 4.0.3 sync, so the patch was taken from nf-core/abotyper's TEMPLATE branch with the repository identity in branch.yml rewritten for this pipeline. That identity is the only pipeline-specific content the template renders into any of the patched workflows, so this is the same change this pipeline's own sync would have produced — but the substituted source is worth a look.

These files conflicted with the patch and were reset wholesale to the nf-core/tools 4.0.3 template version, on the basis that they carry no pipeline-specific content. If this branch had local edits in them, those edits are gone — please review: .github/workflows/branch.yml .github/workflows/linting.yml
Remove vulnerable PR-comment artifact pattern
@github-actions

Copy link
Copy Markdown

YAML linting is failing

To keep the code consistent with lots of contributors, we run automated code consistency checks.
To fix this CI test, please run:

  • Install yaml-lint
  • Fix the markdown errors
    • Run the test locally: yamllint $(find . -type f -name "*.yml" -o -name "*.yaml")
    • Fix any reported errors in your YAML files

Once you push these changes the test should pass, and you can hide this comment 👍

We highly recommend setting up yaml-lint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!

Thanks again for your contribution!

@github-actions

Copy link
Copy Markdown

Markdown linting is failing

To keep the code consistent with lots of contributors, we run automated code consistency checks.
To fix this CI test, please run:

  • Install markdownlint-cli
  • Fix the markdown errors
    • Automatically: markdownlint . --config .github/markdownlint.yml --fix
    • Manually resolve anything left from markdownlint . --config .github/markdownlint.yml

Once you push these changes the test should pass, and you can hide this comment 👍

We highly recommend setting up markdownlint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!

Thanks again for your contribution!

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.

2 participants