Hi Paul, I'm not sure if this was ever resolved, but I think the plan going forward is to start bumping major versions on each release. Would NPM allow such changes in that case?
Cheers, Micah On Wed, Jul 1, 2020 at 9: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 > >
