-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to find actions actions/setup-node@v2 #211
Comments
Yeah same problem here. I now use |
Generally speaking you probably shouldn't point to a release branch of an action. Use a specific version found on the marketplace, otherwise you'll run the risk of breaking changes affecting your production workflows. |
Well I assume no breaking changes will be introduced within a single major version to be honest... |
I wouldn't assume that as you're referencing a branch directly and not a tagged version. Use a tagged version with Dependabot to keep your workflows up to date. If the maintainer forgets to commit something, or is mid-deployment, your workflow could potentially break. |
Hello everyone! |
This is still an issue for me but maybe it's because we use GitHub Enterprise Server 3.0.1 (GHES: hosted in our own servers)? We need to ask whoever installed our GHES to update the installation to pick up the v2 actions, correct? Would you recommend we switch back to the GitHub SAAS? Are customers encouraged to move back to the SAAS? I.e.: are customers like us, who installed GHES starting to transition back to the SAAS GitHub so that they stop having to manage all of that? To me, that sounds like the way to go. In the meantime (until they update our local version of GHES, if that is the issue), I guess I should use the self-hosted actions, right?
The error is:
Thanks!! |
I don't mean to dig grave here, but this issue doesn't seem to be resolved.
|
Hello @Fitmavincent. You specified the wrong version for the setup-node action. It should be |
Thank you very much @dmitry-shibanov. |
…actions#211) Bumps [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) from 4.25.0 to 4.26.0. - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/parser/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v4.26.0/packages/parser) --- updated-dependencies: - dependency-name: "@typescript-eslint/parser" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@dmitry-shibanov This had me stumped for a good ten minutes just now hahaha. Thank you! |
I was trying to upgrade from actions/setup-node@v1 to actions/setup-node@v2.
Following the documentation from the action page i've replaced v1 with v2.
Upon running the action we get the following message.
Is it something with the documentation? Is v2 still in beta? Or which tags should we use?
The text was updated successfully, but these errors were encountered: