chore: Bump r-lib/actions from 2.11.3 to 2.11.4

[dependabot]

Bumps r-lib/actions from 2.11.3 to 2.11.4.

Changelog

Sourced from r-lib/actions's changelog.

v2.11.4 (2025-10-08)

• [setup-r] correctly installs Rtools again on aarch64 Windows, as needed.

v2.11.3 (2025-03-24)

• [setup-r] now supports Rtools45, and installs it by default for R >= 4.5.0.

v2.11.2 (2025-02-19)

• [setup-r] now installs gfortran 14.2 for R 4.5.0 and later (#965).

• [setup-r] now does not use PPM on aarch64 Linux, because PPM does not have binary packages for aarch64 Linux, and it would send x86_64 binarires for aarch64 systems as well.

• [setup-r] now unlinks pkg-config@0.29.2 on macOS silently, to avoid an error from the problem matchers (#973).

• [setup-r-dependencies] now supports dependencies: FALSE (@​eitsupi, #961).

• [setup-r-dependencies] now creates the R_LIBS_USER and R_LIBS_SITE library directories (#974).

• [setup-r-dependencies] now prints the R repo status (#975).

• Example workflows that use renv now call setup-r with r-version: renv, to install the R version declared in the renv.lock file.

v2.11.1 (2024-11-25)

• [setup-r] now unlinks the pre-installed pkg-config brew package to fix a clash with the new pkgconf package (#948).

v2.11.0 (2024-11-09)

• [setup-r-dependencies] parameter pak-version can now be repo or none as well. repo means that the action will install pak from the configured repositories, using install.packages(). repo is appropriate on systems that do not have access to our pak repository on GitHUb. none means that the action does not install pak at all. Use this if you want to install pak yourself manually. Set the R_LIB_FOR_PAK environment variable to point to the library where pak is installed.

• [setup-r] now has a working-directory parameter, to be able to

... (truncated)

Commits

• 6f6e5bc Update NEWS and docs before release (#1026)
• ef7bc5c Support aarch64 Windows (#1025)
• ab09ddf r-devel-test.yaml: allow linux and windows aarch64
• 6b49fef Clarify upgrade values (#1004)
• 4f58f8f Fix a few typos (#1000)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)