Xuanwo opened a new issue, #7897:
URL: https://github.com/apache/opendal/issues/7897

   ## Problem
   
   During the Apache OpenDAL 0.58.0 final release, the tag-triggered `Release 
NodeJS Binding` workflow failed in the publish job.
   
   Run: https://github.com/apache/opendal/actions/runs/29085866719
   
   The failure happened at:
   
   ```shell
   npm install -g npm@latest
   ```
   
   At release time, `npm@latest` resolved to npm 12, whose engine requirement 
did not support the workflow's Node 20 runtime:
   
   ```text
   [email protected] requires node "^22.22.2 || ^24.15.0 || >=26.0.0"
   actual node v20.20.2
   ```
   
   ## Impact
   
   The final Node.js package publish did not complete from the release tag 
workflow. We had to use a temporary release branch that pinned npm to a 
Node-20-compatible major and then dispatch the workflow manually.
   
   Workaround run: https://github.com/apache/opendal/actions/runs/29087192534
   
   ## Expected fix
   
   The Node.js release workflow should avoid floating to an incompatible npm 
major. Either pin npm to a compatible major for the configured Node runtime, or 
update the Node runtime and npm requirement together.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to