Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[JS][Release] Stop re-testing JS packages when uploading to npm

Open
#57 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript, shell
Domain
release

Research direction

Start with npm-release.sh at lines 21-23 and review how JavaScript packages are tested during the upload step. Confirm whether the post-release test can be removed without changing the earlier release verification, and verify that uploading to npm no longer re-runs those tests.

Written by the indexing model from the issue text.

Description

Type: enhancement
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 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

Dominant language
TypeScript
Stars
112
Forks
23
Avg merge
17h 55m
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow-js

All issues in apache/arrow-js

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.