Re: Verify Change Log action failing
Robert Muir <[email protected]> Fri, 3 Jul 2026 08:20:15 -0400
| Newsgroups | gmane.comp.jakarta.lucene.devel |
|---|---|
| Message-ID | <CAOdYfZX6QNvJRda6Bouh=Fi=q2gD_mNVTJnRt_p17W6a3M5zUg@mail.gmail.com> |
I was worried this would find something when upgrading to actions/checkout version. I'd like to change this workflow to not have the security risk, but its a holiday here. Can it wait? On Fri, Jul 3, 2026 at 4:08=E2=80=AFAM Alan Woodward <[email protected]>= wrote: > > Hi all, > > Our Verify Change Log action in GitHub is failing on every PR now with a = permissions error: > > "Error: Refusing to check out fork pull request code from a 'pull_request= _target' workflow. This workflow runs with the base repository's GITHUB_TOK= EN, secrets, default-branch cache scope, and runner access. Fetching and ex= ecuting a fork's code in that trusted context commonly leads to "pwn reques= t" vulnerabilities. To opt in, review the risks at https://gh.io/securely-u= sing-pull_request_target and set 'allow-unsafe-pr-checkout: true' on the ac= tions/checkout step.=E2=80=9D > > I don=E2=80=99t know enough about how actions work to know if changing `a= llow-unsafe-pr-checkout` is the right solution here, or if we need to chang= e the access for this action somehow? > > - Alan > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >