Use relevant metadata file when determining Node.js version #193
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
This workflow job supports projects with multiple npm projects in subfolders of the repository. The version of Node.js to use is determined from the content of the npm metadata file. Previously the workflow always used the file located in the root of the repository. The versioning data in that file won't necessarily be correct for npm projects in subfolders, so the metadata for the individual npm project should be used instead.
per1234
added
type: imperfection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This workflow job supports projects with multiple npm projects in subfolders of the repository. The version of Node.js to use is determined from the content of the npm metadata file. Previously the workflow always used the file located in the root of the repository. The versioning data in that file won't necessarily be correct for npm projects in subfolders, so the metadata for the individual npm project should be used instead.