CI - Tag-release-publish - Use Node.js v18 #310
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
MrChocolatine
force-pushed
the
ci-remove-node-version-use-default-value
branch
from
ce75983 to
fce3ee6
Compare
|
We need this PR approved and merged, the auto-tag & release is blocked due to Node.js v14 being currently used: And we may need the same here as well: DazzlingFugu/ember-feature-controls#261 |
MrChocolatine
force-pushed
the
ci-remove-node-version-use-default-value
branch
from
fce3ee6 to
4483fa7
Compare
MrChocolatine
changed the title
node-version and use default value
|
@DazzlingFugu/emberenos |
Pixelik
approved these changes
Nov 15, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CI
Workflow "tag-release-publish", use Node.js v18 (#310)
Twin PR with: DazzlingFugu/ember-feature-controls#261