-
Notifications
You must be signed in to change notification settings - Fork 215
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: Downgrade execa to 9.1.0 for Node.js 18.18 support #10500
Conversation
Deploying agoric-sdk with Cloudflare Pages
|
.github/workflows/integration.yml
Outdated
@@ -135,8 +135,7 @@ jobs: | |||
path: ./agoric-sdk | |||
- uses: ./agoric-sdk/.github/actions/restore-node | |||
with: | |||
# XXX loadgen not compatible with 18.19 https://github.com/Agoric/agoric-sdk/pull/8365#issuecomment-1848003597 |
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.
pretty sure this was legit https://github.com/Agoric/agoric-sdk/actions/runs/11863590746/job/33065361760?pr=10500
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.
Damn. Then I guess the right fix is instead downgrading execa to e.g. ^9.3.1?
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.
This is the fix I'd really like to see =)
But downgrading execa makes sense for now.
Description
Version ^18.19.0 is required by execa 9.5.1 (which we already use in fast-usdc and a3p-integration/proposals/n:upgrade-next): https://github.com/Agoric/agoric-sdk/actions/runs/11863279067/job/33064414447?pr=10499#step:4:270
error [email protected]: The engine "node" is incompatible with this module. Expected version "^18.19.0 || >=20.5.0". Got "18.18.2"
...and is the LTS version anyway.
Security Considerations
n/a
Scaling Considerations
n/a
Documentation Considerations
n/a
Testing Considerations
There was a comment from last year about Node.js v18.19 incompatibility; integration testing will reveal if it has in fact been resolved.
Upgrade Considerations
It might be time to bump the Node.js ^18.12 prerequisite.