| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
This reverts commit 820128a.
|
Is this reviewable now @Xlient I think we did all the tasks ! |
Sorry, something went wrong.
added link to README * migrated contents of version-file-workflow.yml to versions.yml * further refactored parseNodeVersionFile() & tests * removed type annotations in catch ()
* added fail-fast to strategy in versions.yml * refactored logic in main that was causing test to fail
* fix grammar in README & Advance usage docs * update example in action.yml
Since actions/setup-node#338, GH's setup-node Action understands `.nvmrc` files. This makes our `guardian/actions-setup-node` fork somewhat redundant now. Move to GH's Action so we can deprecate our fork.
Bumps [typescript](https://github.com/Microsoft/TypeScript) from 4.5.2 to 4.5.3. - [Release notes](https://github.com/Microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v4.5.2...v4.5.3) --- updated-dependencies: - dependency-name: typescript dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Description
In scope of this pull request we add Node.js version file support. This pull request introduces new optional input: node-version-file, that accepts path (relative to repository root) to file containing Node.js version (for example .nvmrc).
The action will search for the Node.js version file and read the Node.js version if the file exists. If both inputs node-version and node-version-file are specified, the action will throw a warning and the node-version input will be used.
Example of yml
Related issue: #32
What's done: