You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently it happens during the "Set up python" phase of "Run pkgcheck" step.
It seems like to be caused by depending on github:actions/setup-python#v2 while it seems already fixed in v4 of that project.
I'd be happy to send a PR to bump the version of the dependency, but I can't judge the full implications of that change, so I decided to open issue for now.
The text was updated successfully, but these errors were encountered:
If I understand correctly, the dependencies here are bundled, and described in package.json. Which this means it might be enough to simply regenerate files like package-lock.json and dist/index.js without any actual code changes.
I will try to open a draft pull request about that to gather further feedback.
On October 11, 2022, we annouced plans to deprecate the save-state and set-output workflow commands on May 31, 2023. We have since decided to postpone the removal given the amount of usage we are still seeing with these commands.
Workflows using save-state or set-output in their workflows will continue to work as expected, however, a warning will appear under annotations indicating the planned deprecation. We recommend customers using these commands to upgrade their workflows to use environment files.
The following warnings started to show up in the annotations on each run during
Apparently it happens during the "Set up python" phase of "Run pkgcheck" step.
It seems like to be caused by depending on
github:actions/setup-python#v2
while it seems already fixed inv4
of that project.I'd be happy to send a PR to bump the version of the dependency, but I can't judge the full implications of that change, so I decided to open issue for now.
The text was updated successfully, but these errors were encountered: