Skip to content

chore(deps): bump r-lib/actions/setup-r-dependencies from 2.11.4 to 2.12.1#68

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/github_actions/r-lib/actions/setup-r-dependencies-2.12.1
Open

chore(deps): bump r-lib/actions/setup-r-dependencies from 2.11.4 to 2.12.1#68
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/github_actions/r-lib/actions/setup-r-dependencies-2.12.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 15, 2026

Copy link
Copy Markdown
Contributor

Bumps r-lib/actions/setup-r-dependencies from 2.11.4 to 2.12.1.

Changelog

Sourced from r-lib/actions/setup-r-dependencies's changelog.

v2.12.1 (2026-06-23)

  • [setup-r] now avoids a warning about an url.parse() deprecation (#1074).

  • [setup-r-dependencies] now uses quarto-dev/quarto-actions v2.2.0 (@​jdblischak, #1076).

  • Examples: test-coverage.yaml now uses codecov/codecov-action v7 (@​shikokuchuo, #1081).

  • New example claude-investigate.yaml workflow (@​DavisVaughan, #1084).

v2.12.0 (2026-04-29)

  • All node.js actions use node 24 now. Relatedly, all example workflows use recent versions of actions that use node 24.

  • [setup-r] now uses use-public-rspm: true by default on Linux and Windows. macOS binaries require further opt-in with use-public-rspm: always.

  • It is now possible to require actions to be pinned to a full-length commit SHA in repositories using r-lib/actions (#1070).

  • [setup-pandoc][setup-r-dependencies] now default to Pandoc version 3.8.3.

  • [setup-r-dependencies] now includes the R architecture in the cache key, so caches for macos-15 (Apple Silicon) and macos-15-intel (Rosetta/x86_64) no longer collide (#1035).

  • [setup-r] run apt-get update without -qq on Linux, to make debugging update failures easier (#1058).

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

... (truncated)

Commits

Dependabot compatibility score

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 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)

Bumps [r-lib/actions/setup-r-dependencies](https://github.com/r-lib/actions) from 2.11.4 to 2.12.1.
- [Release notes](https://github.com/r-lib/actions/releases)
- [Changelog](https://github.com/r-lib/actions/blob/v2-branch/NEWS.md)
- [Commits](r-lib/actions@6f6e5bc...d3c5be5)

---
updated-dependencies:
- dependency-name: r-lib/actions/setup-r-dependencies
  dependency-version: 2.12.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 6703843fe6d5b00932de772deba0c43474fa83f3.

  • Head SHA: 6703843fe6d5b00932de772deba0c43474fa83f3

  • Workflow run: 29539031336

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (3 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow (3 files)"]
  R1 --> V1["actionlint plus required checks"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 6703843fe6d5b00932de772deba0c43474fa83f3
  • Workflow run: 29539031336
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 6703843fe6d5b00932de772deba0c43474fa83f3.

  • Head SHA: 6703843fe6d5b00932de772deba0c43474fa83f3

  • Workflow run: 29539031336

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (3 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow (3 files)"]
  R1 --> V1["actionlint plus required checks"]
Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant