Commitlint: [question] why versions 10 and 11 published under "next" tag on NPM?

Created on 9 Sep 2020  路  2Comments  路  Source: conventional-changelog/commitlint

Expected Behavior

All major versions expected to be published under the "latest" tag on NPM

Current Behavior

All major versions published under the "next" tag on NPM

question
Source
picture Jagget

Most helpful comment

Hey @Jagget , valid question.

We do this most of the times before publishing new latest versions.
In this way some people can test the next version and if there's no negative feedback we usually switch it to be latest within 2-6 weeks or so.
In the current case we wanted to switch directly to v11 that's why v9.1.2 is still latest atm.
v11 will be released soon.

picture escapedcat on 10 Sep 2020
👍2

All 2 comments

Hey @Jagget , valid question.

We do this most of the times before publishing new latest versions.
In this way some people can test the next version and if there's no negative feedback we usually switch it to be latest within 2-6 weeks or so.
In the current case we wanted to switch directly to v11 that's why v9.1.2 is still latest atm.
v11 will be released soon.

escapedcat picture escapedcat on 10 Sep 2020
👍2

v11.0.0 is released as latest

escapedcat picture escapedcat on 13 Sep 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

foray1010 picture foray1010  路  3Comments
yenbekbay picture yenbekbay  路  5Comments
nareshbhatia picture nareshbhatia  路  5Comments
whizark picture whizark  路  3Comments
topocount picture topocount  路  3Comments