Deprecation warnings

[jpfeuffer]

Run ./setup-nextflow/subaction
Input version '24.10.5' resolved to Nextflow v24.10.5
Downloaded `nextflow` to /opt/actions-runner/_work/_tool/nextflow/24.10.5/x64 and added to PATH
(node:3748) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
(Use `node --trace-deprecation ...` to show where the warning was created)

[jpfeuffer]

Might be due to a private runner with a different node version. But probably good to check.

[jpfeuffer]

Wait, 551 commits since last release? And I can't view changes because master and 2.0 have unrelated histories?
Something is very wrong with this repository.

Just wanted to check if this is solved on master.

[MillironX]

(node:3748) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead

fs.rmdir() is not used in this codebase (maybe fs.rmdirSync() is triggering the warning).

551 commit since last release

That's the power of Rennovate (#42). Commits are a bad way to measure progress, too.

master and 2.0 have unrelated histories?

This is expected. See https://github.com/nf-core/setup-nextflow/blob/master/.github/CONTRIBUTING.md#build-process.

The tag contains the compiled JavaScript code that GitHub Actions runs, while master contains the developer-facing code.

Something is very wrong with this repository.

The JavaScript action will be deprecated just as soon as someone steps up to finish implementing #179. You're welcome to contribute.