@peter-evans Please have a look

Hi @thijsvtol

Apologies for the slow response.

The deprecation message is unrelated to the error. "Resource not accessible by integration" is usually caused by the process not having access to the token it needs to perform the repository dispatch. This can happen if (for example) the workflow is triggered by a PR from a fork. For security reasons, some actions don't have access to tokens.

I'll look at the deprecation warning later when I have time, but I just wanted to let you know that it didn't cause the error.

Hi @peter-evans, I'm aware of the deprecation warning is not causing the error. However, it still needs to be fixed ;)

@thijsvtol It's likely it is deprecated as the message suggests, but strangely I don't see that warning. Can you show me your workflow or a run where this occurs?

See a run I executed today: https://github.com/peter-evans/repository-dispatch/actions/runs/6082839902/job/16501443779

I guess it will only appears when an error occurs :D

Of course, that makes sense. 🤦‍♂️

Looks good to me. Thank you for contributing!