-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add Option to Enable corepack #546
Conversation
I can't figure out why the test is failing based on the other tests... 😕 |
Is it possible to completely remove pnpm/action-setup with this? What I mean is - uses: actions/node-setup@v3
with:
node-version: "18"
corepack: true
cache: "pnpm" would be enough with no other actions so no pnpm installed at all before node-setup? I would think so because node is installed, corepack enable is run, and then after that the caching is setup. Thus the first time node-setup calls pnpm for the caching, corepack should install pnpm. If so, I think the documentation in |
@beeequeue Thank you for this contribution! When do you think this will get merged? If so? |
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.
Looks good
I also have a 32G dcim that i user at beginning of build. Would that he of user? |
Should i switch dcim cards? |
Presumably after the test starts passing, and I can't get it to on my Windows machine 😢 |
So what an I looking |
So what an I looking at here? |
BeeeQueue/setup-node#2
Co-authored-by: Steven <steven@ceriously.com>
Co-authored-by: Steven <steven@ceriously.com>
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.
🎉
@beeequeue What's your ETA on merging this? |
@jtbandes it's not rejected; I just said it's not a priority yet: #531 (comment) It looks like some of the tests were added are failing. @beeequeue I don't know a lot about this domain, but are you sure When I have an issue with an Actions workflow I can't reproduce locally, I usually end up having to add some |
I manged to reproduce it, but got no idea why it's happening I'm not very motivated to try to figure out why the tests fail after the rebase, nothing is wrong and it works perfectly so I'm just gonna use my branch in my projects. |
Superseded by #651 |
…ctions#546) Bumps [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) from 6.5.0 to 6.6.0. - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.6.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>
Description:
Adds the
corepack
option, which iftrue
will runcorepack enable
to enable corepack.You can see a test run of it here: https://github.com/BeeeQueue/arm-server/runs/7380286080?check_suite_focus=true
Related issue:
Closes #531
#480 - @dmitry-shibanov says that this change would not bring enough value to users, but I agree with @shellscape that being able to move most if not all of the node setup into one step is quite nice 🙂
#482 - That PR adds automatic support for it which could potentially be breaking, this PR adds an option which should not break anything
Check list: