fix: Use v14 LTS docker image to fix issues since v15 which is not LTS and the node:slim image has been upgraded to #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… the node:slim image has been upgraded to
Contributor
Author
|
I have just tested this by pointing our repo at my fork + fix branch, it works :) |
Contributor
Author
|
@gr2m No problem! Can you update the version tag please? |
Contributor
|
I'm looking into it right now. It should have all been automated, but it's all so old, I'm updating it all to the latest right now and will release a new version shortly |
|
🎉 This PR is included in version 1.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Contributor
|
releases are now automated and are continuously pushed to the - uses wip/action@v1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should fix issue #26
node:slim docker image has been updated to Node v15. So it's either use v14 which gets my vote as it is the LTS version or regenerate the package-lock.json file with Node 15 (assumed alternate fix).