-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node:slim base image update seems to have broken action #23
Comments
Does anyone know of a workaround other than disabling the action? |
There are some good recommendations on https://stackoverflow.com/a/64497384/69002 but all of them require changes to the Dockerfile. So you'd need to fork or wait for node to fix nodejs/docker-node#1379 I think. |
Looks like the whole 15-slim series has the issue
|
Co-authored-by: Raimondas Rimkevičius (aka MekDrop) <[email protected]>
@hross is there any timeline to get this fixed? Thanks! |
I think there are 2 things important here, when fixes will be merged, and how they will be released, will it be under 1.0.0 because no functionality changed? Updating version in several different repos sounds like a task noone wants to do |
Setup version: 2
updates:
- package-ecosystem: github-actions
directory: "/"
schedule:
interval: daily
open-pull-requests-limit: 10 in your repos and it'll update if needed when an update becomes available. |
@nemchik awesome, was not aware dependabot supports actions. I still would need to add it to all the repos :( |
+1 for this issue. We use actions/first-interaction greetings for our YOLOv5 repo: actions/first-interaction is now failing though, i.e. https://github.com/ultralytics/yolov5/runs/1314359799?check_suite_focus=true Full error message is:
|
The node:slim base image was updated ~7 hours ago, and all first-interaction actions seem to have started failing since then. The error that I'm seeing during the container build is this:
I suspect it's related to these deprecation warnings prior to the base image getting changed:
The text was updated successfully, but these errors were encountered: