CI failed and v0.5.1 was not published

[teppeis]

From CI#217, CI failed.
v0.5.1 was not published.

I don't know if this is the cause, but on ubuntu-22.04 with image version 20240403.1.0 or later, the node v16 job is failing to find yarn.

[SunsetTechuila]

From CI#217, CI failed.

this a lint action that was triggered by the pull request, it has nothing to do with releases

v0.5.1 was not published.

it was - https://www.npmjs.com/package/eslint-plugin-import-x/v/0.5.1

I don't know if this is the cause, but on ubuntu-22.04 with image version 20240403.1.0 or later, the node v16 job is failing to find yarn.

see actions/setup-node#1075

[SukkaW]

Yeah, it seems that Node.js 16's corepack can't install yarn. I am going to work on it.

[SunsetTechuila]

Node.js 16's corepack can't install yarn.

No, it is the latest Corepack can't fetch anything because it tries to use Node's built-in fetch, which was only added in Node v18. Why is the latest Corepack being used? Because corepack enable is run before setting up the target Node.

I am going to work on it.

The only solution: actions/setup-node#1075 (comment)

[SukkaW]

@SunsetTechuila

Thanks for providing so many details and context!

Would you like to create a PR to help us fix the CI?

[SunsetTechuila]

@SukkaW done

[teppeis]

Thank you!