Since publishing artifacts to NPM is somewhat independent from the Apache source release, if you aren't ready to push to NPM then the release manager can just not push the artifacts
Note that the plan hasn't been to go from 1.0.0 to 1.1.0, rather that almost every Apache release (aside from patch releases) would be a major version bump, so the next release after 1.0.0 is 2.0.0. On Wed, Jul 1, 2020 at 11:23 AM Paul Taylor <ptaylor.apa...@gmail.com> wrote: > > The TypeScript compiler has made breaking changes in recent releases, > meaning we can't easily upgrade past 3.5 and projects on 3.6+ can't > compile our types. > > I'm working on upgrading our tsc dependency to 3.9. The fixes could > include a few backwards-incompatible API changes, and might not be done > in time for the general Arrow 1.0 release. > > JS shouldn't block the 1.0 release, so can we exclude JS from 1.0 if the > fixes aren't ready by then? npm's semantic versioning allows breaking > changes in any version before 1.0, but not between minor versions after > 1.0. I've heard directly from some of our JS users who'd prefer if we > made these changes before bumping to 1.0 on npm. > > Thanks, > > Paul >
