dask
Remove need for temporary workaround in autotag action
The Auto Tag action appears to be broken: https://github.com/dask/dask-docker/actions/runs/7228513483/job/19698075758
As a result, the latest available image is 2023.11.0, which lags behind by two releases.
Thanks for catching @hendrikmakait. cc @jacobtomlinson @charlesbluca -- do either of you have bandwidth to look into this one?
Okay, so https://github.com/dask/dask-docker/pull/305 put in place a temporary workaround and the autotag workflow is now working again (thanks again for spotting @hendrikmakait).
Let's keep this issue open, but change the purpose to "Remove need for temporary workaround in autotag action"
Thanks for the quick fix @jrbourbeau! Based on the warnings while building the autotag action:
#9 3.732 npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=14.0"} (current: {"node":"13.14.0","npm":"6.14.4"})
#9 3.732 npm WARN notsup Not compatible with your version of node/npm: [email protected]
#9 3.732 npm WARN notsup Unsupported engine for @fastify/[email protected]: wanted: {"node":">=14"} (current: {"node":"13.14.0","npm":"6.14.4"})
#9 3.732 npm WARN notsup Not compatible with your version of node/npm: @fastify/[email protected]
#9 3.732 npm WARN @octokit/[email protected] requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
I'd assume that some unpinned dependencies are now getting pulled in with a conflicting node version and causing issues, in this case undici; it's worth noting that commits have been getting pushed to master up until 9 months ago, so it's possible that this issue has already been resolved and just hasn't been pushed out in a release or tag?
I'd assume that some unpinned dependencies are now getting pulled in with a conflicting node version and causing issues
Yeah, that seems to be what folks are talking about in the issues linked to in https://github.com/dask/dask-docker/pull/305
It's been over three years since there's been a new release of ButlerLogic/action-autotag and, as you mentioned, over nine months since any commits have been added to the project. Is there another action that does the same thing and is more actively maintained? Might be time to switch to another action if possible