ci(workflows/ci): setup node before enabling corepack

[JounQin]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 057794c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[github-actions]

size-limit report 📦

Path	Size
./lib/index.js	2.23 KB (0%)
	0 B (+100% 🔺)

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	12.2 kB	sindresorhus
npm/[email protected]	None	0	8.9 kB	zensh
npm/[email protected]	environment	0	8.13 kB	sindresorhus
npm/[email protected]	None	0	6.17 kB	sindresorhus
npm/[email protected]	None	0	314 kB	dmitrysoshnikov
npm/[email protected]	filesystem	0	17.3 kB	isaacs
npm/[email protected]	None	0	9.96 kB	isaacs

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Install scripts	npm/[email protected]	Install script: install Source: node build.js	package.json	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[JounQin]

@ljharb Did you change my permission on this repository? I can no longer merge this PR with privilege.

[ljharb]

You have “maintain” permission; it seems like you should be able to merge it. Is the socket failure blocking it?

[JounQin]

OK, I'm not so familiar with merge queue feature, it seems not blocking now.

[JounQin]

@ljharb I'm not sure why npm permission is not recognized in CI, and I don't have permission to check the secrets used in CI any longer.

https://github.com/import-js/eslint-import-resolver-typescript/actions/runs/9928981640/job/27425949199

[ljharb]

the NPM_TOKEN secret exists, but its value can’t be seen, only changed. I’m not familiar with changesets but i wouldn’t expect anything to have changed unless your own npm token changed. Hit me up privately and we can get it sorted.