This repository has been archived by the owner on Dec 12, 2022. It is now read-only.
Tag builder only builds node-16. #70
Merged
Conversation
This file contains 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
Edge / main builder will still build both version
chriswk
force-pushed
the
task/only-build-node-16
branch
from
aa4f669 to
d3575c1
Compare
thomasheartman
approved these changes
Jun 17, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Edge / main builder will still build both version
We have been running unleash node16 in production since January, this drops building 14-alpine altogether for our tagged releases. Due an incorrect configuration, we've been publishing the node version that was last in our matrix, which happened to be 16 anyway, this makes it more explicit.