apache / arrow

Apache Arrow is the universal columnar format and multi-language toolbox for fast data interchange and in-memory analytics
https://arrow.apache.org/
Apache License 2.0
14.5k stars 3.53k forks source link

[JS][Release] Wrong -.tar.gz name on arrow2csv fails when publishing #44585

Open raulcd opened 1 day ago

raulcd commented 1 day ago

Describe the bug, including details regarding any error messages, version, and platform.

When publishing to npm the JavaScript implementation for 18.0.0 I saw the following error on one of the packages

npm notice === Tarball Contents === 
npm notice 248.2kB Arrow.js    
npm notice 23.4kB  arrow2csv.js
npm notice 13.3kB  arrow2csv.ts
npm notice 20B     package.json
npm notice === Tarball Details === 
npm notice name:                                                  
npm notice version:                                               
npm notice filename:      -.tgz                                   
npm notice package size:  66.6 kB                                 
npm notice unpacked size: 285.0 kB                                
npm notice shasum:        ac29699beca57a8c8a20fef88d9c3d2b83934dce
npm notice integrity:     sha512-2vcxFjK8cZ+Q5[...]/6uMhk+7VGK8Q==
npm notice total files:   4                                       
npm notice 
npm notice Publishing to https://registry.npmjs.org/ with tag latest and default access
npm ERR! code EBADSEMVER
npm ERR! invalid semver: 

There seems to be a bad filename generated from the log -.tgz but I am unsure on what happens. In order to publish I run the script:

dev/release/post-07-js.sh 18.0.0

The version seems to be published sucessfully apart from this: https://www.npmjs.com/package/apache-arrow/v/18.0.0

Component(s)

JavaScript, Release

raulcd commented 1 day ago

@domoritz @trxcllnt any idea what happened there?

domoritz commented 1 day ago

I don't know much about the publishing process. npm ERR! invalid semver: seems to indicate that there is no version detected. The command looks right and I don't see anything off in the scripts either.

raulcd commented 1 day ago

To me the issue seems to be related to a wrongly generated filename and it fails because the version can't be detected: The filename generated seems to be -.tgz