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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: Use setup node instead of volta action #7763

Merged
merged 3 commits into from
Apr 6, 2023

Conversation

AbhiPrasad
Copy link
Member

As per https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#node-version-file, actions/setup-node will use the volta definition for node version - so we should be ably to safely switch away from volta.

Closes #7690

@AbhiPrasad AbhiPrasad requested a review from mydea April 5, 2023 16:17
@AbhiPrasad AbhiPrasad marked this pull request as ready for review April 5, 2023 17:28
@AbhiPrasad AbhiPrasad requested review from a team and lforst and removed request for a team April 5, 2023 17:30
@mydea
Copy link
Member

mydea commented Apr 6, 2023

Q: Does that also use the volta pinned yarn version? Or do we need to make sure this is the correct one?

@AbhiPrasad
Copy link
Member Author

Q: Does that also use the volta pinned yarn version? Or do we need to make sure this is the correct one?

It seems action/setup-node have yarn pre-installed to a certain version. As per the docs, this is Yarn 1.22.19, what we have hard pinned via volta.

Copy link
Member

@mydea mydea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice! hopefully this will fix the node caching stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cache node on CI/Volta to avoid flakiness
3 participants