Skip to content

Nested quarto action in setup-r-dependencies@v2 breaks workflow in restricted Organization setup #901

@solmos

Description

@solmos

Is your feature request related to a problem? Please describe.
My GitHub Organization only allows to use specific minor release versions (vX.X.X) of untrusted third-party actions, and they consider that quarto-dev/quarto-actions/setup falls under this category (r-lib actions do not). Thus the nested quarto-dev/quarto-actions/setup@v2 action in setup-r-dependencies@v2.10.0 introduced in 67f8747 causes all workflows to fail due to the version used for the quarto action. This occurs even if we set install-quarto: false, since the workflow will first check if all the actions required by a given action can be downloaded.

Describe the solution you'd like
If this dependency in quarto-dev/quarto-actions/setup is desirable, a solution would be to include an input parameter in r-lib/actions/setup-r-dependencies for specifying the version of the quarto action.

Describe alternatives you've considered
We could use setup-r-dependencies@v2.9.0 but we would be stuck with an outdated action forever.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions