-
Notifications
You must be signed in to change notification settings - Fork 2
chore: [STMS-4062] Migrate js-tools to pnpm #198
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
base: master
Are you sure you want to change the base?
Conversation
- uses: pnpm/action-setup@v4 | ||
with: | ||
version: 10 | ||
- uses: umidbekk/actions/prepare-node-repo@v2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SiriusCrain Did you have time to check if we can use prepare-node-repo@ without pnpm/action-setup? And can you replace umidbekk/actions/prepare-node-repo@v2
with superdispatch one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will check
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I can replace umidbek's package, but since other workflows were requiring addin pnpm-action...
"node": ">=12" | ||
"node": ">=20" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SiriusCrain IIIRC, not all our repo require node>=20, and it could become a problem during migrations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can update node version in our other repos, and then use upgraded js-tools build, for now we can use current (0.8.0)
No description provided.