You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "raulcd (via GitHub)" <gi...@apache.org> on 2025/05/26 22:40:27 UTC
[I] [JS][Release] Stop re-testing JS packages when uploading to npm [arrow-js]
raulcd opened a new issue, #57:
URL: https://github.com/apache/arrow-js/issues/57
### Describe the enhancement requested
As part of the release process we test all the packages on several CI jobs for different OS and environments.
We also do a lot of integration tests and release verification.
As part of the release verification we do test JS packages.
Once the release has been approved we are executing the [npm-release.sh](https://github.com/apache/arrow/blob/main/js/npm-release.sh#L21-L23) where we re-test again JS.
JS is the only package were once the release is approved we test again. Is this really necessary?
The post-release task for JS could be reduced if we avoid testing which feels unnecessary at this point.
### Component(s)
JavaScript, Release
--
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: issues-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org