Repository navigation
What's on version 3.3.3333? #30032
Description
My apologies if this is not the right issue type. I just think that needs urgent attention as it could mean npm is compromised (which is not unheard of).
I got this from my project.
Surprised, I went to the npm page for typescript and got this.
Is this expected?
Activity
tkausl commentedon Feb 22, 2019
2c02f13
RyanCavanaugh commentedon Feb 22, 2019
We published
3.3.3333because, unfortunately, npm rejected our PR to allow versions with an infinite number of repeating digits.dashmug commentedon Feb 22, 2019
Thank you for the response. It is expected then. I'll close this.
fictitious commentedon Feb 22, 2019
Ryan Cavanaugh (@RyanCavanaugh) you'd have better chances with npm if you went with PR allowing such versions to be published on GitHub first
RyanCavanaugh commentedon Feb 22, 2019
We had an offline conversation, but couldn't come to an agreement about whether
4.9999...should be equivalent to5.0or not.jacobwgillespie commentedon Feb 22, 2019
Sorry if I'm just missing a joke here, but I'm probably not the only one still confused. 🙃
Given that automated tools like Greenkeeper/Dependabot etc are now recommending upgrading from
3.3.3to3.3.3333, is this new version legit? We're trying to audit this from a security perspective, and this kind of release is unusual behavior for semver, etc. Also I think this version probably blocks any automated upgrades to3.3.4since 4 is less than 3333.Besides this issue, I can't find anything relating to what this is or why it was published, and there are actual code changes in the diff between the the
3.3.3and3.3.3333versions.DanielRosenwasser commentedon Feb 22, 2019
Sorry, humor aside, the new version is legit.
jacobwgillespie commentedon Feb 22, 2019
Does that mean there will be no version
>=3.3.4 <3.3.3333?RyanCavanaugh commentedon Feb 22, 2019
Correct. Any future version on the
3.3line will be something like3.3.4000weswigham commentedon Feb 22, 2019
Or more likely
3.3.33333given what we've already done tbh.Jessidhia commentedon Feb 22, 2019
Missed an opportunity to have
3.1.4159🤔alexeagle commentedon Feb 22, 2019
I know you guys don't believe in semver but now you have to introduce floating point errors into it? I feel like this change is just 1/3 whimsical.
zaoqi commentedon Feb 23, 2019
qiaodaima
讓我想起了Microsoft Windows版本號，雖然我現在不用Microsoft Windows，也不用wine，同時也在試圖刪除GNU和Linux和BSD（指我可能將實現一個運行於ARM,Intel芯片之上的整個內核作為一個我設計的編程語言解釋器所以不一定需要MMU的內核及操作系統）。
chase-moskal commentedon Feb 24, 2019
Jessica Franco (@Jessidhia)
we can still have hope for
typescript@3.14.1592we11adam commentedon Mar 1, 2019
This version number is in no way a joke I can appreciate because I literally spent a few minutes reading this issue and 2c02f13 trying to figure it out only to find out it's really meaningless.
Can we stop this from happening again, please? Thanks! Daniel Rosenwasser (@DanielRosenwasser)
TheReincarnator commentedon Mar 3, 2019
Not very professional, misleading, irritating. And not consistent in terms of semver. This is why people outside the JS/TS community are taking it not serious.
jkoepcke commentedon Mar 11, 2019
I would really like to know how many developer hours have been wasted worldwide investigating about this version number... with great power comes great responsibility :)
KissBalazs commentedon Mar 11, 2019
Nice to see that other professionals still use their highschool homework versioning systems as well.
sysmat commentedon Mar 14, 2019
Probably in semantic versioning is legit, but it is strange
forresthopkinsa commentedon Sep 23, 2019
So many complainers. I came across this issue because I saw the joke in my NPM logs and I wanted to know where to direct my appreciation. Made me chuckle. We don't need to be so serious all the time.