@jclem

and please, after finishing that PR - can we release a new version?

Well, leaving it within v3 would help to not break existing builds... At the end of the day, there's nothing changing in the API. But I guess that's what you mean after all.

Well, leaving it within v3 would help to not break existing builds... At the end of the day, there's nothing changing in the API. But I guess that's what you mean after all.

Of course, I meant to keep V3 pointed to the new master.
Thanks for the clarification

I wonder if it wouldn't make more sense to just fork this and start using forked versions?

I wonder if it wouldn't make more sense to just fork this and start using forked versions?

I think not
It will be only a temporary workaround. The correct way is to wait (or ping @jclem somehow) for the fix to be in the master.

@guyarb Can you provide a bit more context on what's being updated in your PR description? The latest release v3.0.1 has the required actions-core update, which should fix failing workflows. I've also released an update with the latest Octokit dependencies in v3.1.0.

My bad, meant to hit "Comment" and hit "Close with comment" on accident.