Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is the yarn version installed configurable? #74

Closed
johnnyreilly opened this issue Oct 22, 2019 · 3 comments
Closed

Is the yarn version installed configurable? #74

johnnyreilly opened this issue Oct 22, 2019 · 3 comments
Labels
question Further information is requested

Comments

@johnnyreilly
Copy link

Heya!

Thanks for your wonderful action 馃

I'm using it to power the GitHub Action that runs tests on ts-loader. We recently bumped on an issue with yarn: yarnpkg/yarn#7584

That was fixed in yarn v1.19.1 and I was left pondering how to upgrade the version of yarn that this action seems to install. See my ponderings here:

TypeStrong/ts-loader#1026 (comment)

I was able to resolve the issue by introducing this:

      - name: upgrade yarn
        run: npm install yarn -g

which upgrades to the latest and greatest yarn. You see... success!:

https://github.com/TypeStrong/ts-loader/pull/1027/checks?check_run_id=270427331

My question is, how is yarn installed by this action? And assuming I'm correct that it is, is it configurable to ensure that it's the latest and greatest? I'm wondering whether the course of action I've followed is the "best way". Or if there's another?

Thanks again for your wonderful action!

@johnnyreilly johnnyreilly changed the title yarn version Is the yarn version installed configurable? Oct 22, 2019
@chingc
Copy link

chingc commented Oct 23, 2019

I had a problem that was also fixed in v1.19.1. You can use the policies sub-command to set the yarn version. The snippet below is what I use to grab the latest version.

- name: Install
  run: |
    yarn policies set-version
    yarn install --frozen-lockfile

@vprasanth
Copy link

I had a problem that was also fixed in v1.19.1. You can use the policies sub-command to set the yarn version. The snippet below is what I use to grab the latest version.

- name: Install
  run: |
    yarn policies set-version
    yarn install --frozen-lockfile

This is good, but I think you should run this command locally and commit the .yarn and .yarnrc files into the repo. Now, no matter what version of yarn is used in the CI it should switch to using the packaged version. The same goes for team members.

@dmitry-shibanov dmitry-shibanov added the question Further information is requested label Oct 27, 2021
@dmitry-shibanov
Copy link
Contributor

Hello everyone. Thank you for all your responses.

Actually the action does not install yarn. Yarn is preinstalled on the hosted images. You can change it version as you described or please refer to the documentation.

For now I'm closing the issue. If you have any concerns feel free to ping us.

krzyk pushed a commit to krzyk/setup-node that referenced this issue Apr 11, 2023
deining pushed a commit to deining/setup-node that referenced this issue Nov 9, 2023
Bumps [axios](https://github.com/axios/axios) from 0.19.2 to 0.21.0.
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/master/CHANGELOG.md)
- [Commits](axios/axios@v0.19.2...v0.21.0)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants