Skip to content

Was v3.6.2 released on npm on accident? #33122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ethanneff opened this issue Aug 28, 2019 · 5 comments
Closed

Was v3.6.2 released on npm on accident? #33122

ethanneff opened this issue Aug 28, 2019 · 5 comments
Labels
Question An issue which isn't directly actionable in code

Comments

@ethanneff
Copy link

ethanneff commented Aug 28, 2019

Has 3.6.2 been released? It shows up in NPM https://www.npmjs.com/package/typescript

In Github, version 3.6+ is still in RC https://github.com/microsoft/TypeScript/releases

@ethanneff ethanneff changed the title 3.6.2 released? Was 3.6.2 released? Aug 28, 2019
@ethanneff ethanneff changed the title Was 3.6.2 released? Was v3.6.2 released on npm on accident? Aug 28, 2019
@arutkowski00
Copy link

arutkowski00 commented Aug 28, 2019

It looks like there's something strange going on in distribution tags.

beta: 3.6.0-beta
rc: 3.6.1-rc
latest: 3.6.2
next: 3.7.0-dev.20190828

There's no 3.6.0 or 3.6.1 in latest.

EDIT: Ok, it is actually a stable release: https://github.com/microsoft/TypeScript/releases/tag/v3.6.2

I'm worried about skipping these versions and jumping straight to 3.6.2. That can confuse some people.

@RyanCavanaugh RyanCavanaugh added the Question An issue which isn't directly actionable in code label Aug 28, 2019
@RyanCavanaugh
Copy link
Member

3.6.2 is also intentionally the version number.

@ethanneff
Copy link
Author

ethanneff commented Aug 28, 2019

It's intentional. See https://github.com/microsoft/TypeScript/releases/tag/v3.6.2 / https://devblogs.microsoft.com/typescript/announcing-typescript-3-6/

That release (17mins ago) was not live when I posted this issue (26mins ago). So NPM updates before Github Releases.

Good to know. Thanks.

@RyanCavanaugh
Copy link
Member

The process occurs in a stochastic order with nondeterminstic delays because humans are pushing the buttons 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question An issue which isn't directly actionable in code
Projects
None yet
Development

No branches or pull requests

3 participants