Closed atomicgamedeveloper closed 2 weeks ago
The other layers may eventually stop working unless the original repository reactivates.
@atomicgamedeveloper what does this mean? I thought the layers are independent!
Please upgrade the node to v22.x and yarn to the latest version. Please also upgrade the dependencies and layers to their latest versions.
The other layers may eventually stop working unless the original repository reactivates.
@atomicgamedeveloper what does this mean? I thought the layers are independent!
The other feature layers come from the same inactive repository, so they may face similar issues down the line when we rebuild. A simple solution is just to replace all the sources to the active one.
Please upgrade the node to v22.x and yarn to the latest version. Please also upgrade the dependencies and layers to their latest versions.
Will do now.
Code Climate has analyzed commit a94ad405 and detected 0 issues on this pull request.
View more on Code Climate.
There is a new PR #1063 that is equivalent to this PR.
Pull Request Template
Title
Fixes the stalling dev container
Type of Change
Description
I exchanged the
ghcr.io/devcontainers-contrib/features/mkdocs:2
which derives from a currently inactive repo to the corresponding layer from the active fork of it, https://github.com/devcontainers-extra/features?tab=readme-ov-file.Testing
I successfully have built the dev container. This was infeasible before.
Impact
Additional Information
Issue discussing this: https://github.com/devcontainers-contrib/features/issues/623
Checklist