4.0.0 · debug-js/debug@7fb104b · GitHub

Commit

4.0.0

Browse files

Loading branch information

Qix- committed Sep 11, 2018

1 parent 84e41d5 commit 7fb104b

package.json

-Original file line number
+Diff line change
@@ -1,6 +1,6 @@
     {
       "name": "debug",
-      "version": "3.2.1",
+      "version": "4.0.0",
       "repository": {
         "type": "git",
         "url": "git://github.com/visionmedia/debug.git"
@@ Expand Down @@

6 comments on commit `7fb104b`

rarkins commented on `7fb104b` Sep 11, 2018

@Qix- which release is meant to be "latest"? 4.0.0 was briefly published as latest but now 3.2.4 is latest once it was published.

Member Author

Qix- commented on `7fb104b` Sep 11, 2018

@rarkins 4.0.0. Whatever is telling you 3.2.4 is latest is bugged - releases that are a higher semver version are "latest" as long as they're not tagged as -pre or some other pre-release identifier.

If you're seeing things break, check out #603 (comment) for more information on the versions that are released.

rarkins commented on `7fb104b` Sep 11, 2018

@Qix- you seem to misunderstand how npm works, I will try to help you in the other thread

Member Author

Qix- commented on `7fb104b` Sep 11, 2018 •

edited

@rarkins I know very well how npm works, thanks. There's no need to be rude or condescending.

Please check my response in the other thread.

rarkins commented on `7fb104b` Sep 11, 2018

@Qix- I said "misunderstand" because this statement is a misunderstanding:

releases that are a higher semver version are "latest" as long as they're not tagged as -pre or some other pre-release identifier.

npmjs does not have logic that resolves "what is the highest stable version published?" and make that highest one latest. Instead it uses whatever was the most recent stable tag published, assuming you don't publish it with an explicit tag.

The correct way to state npm's behaviour is:

Whenever a stable semver version is published to npmjs without an explicit tag, it will take over the latest tag for that package even if it is a lower semver version than the currently tagged latest release.

Also: npmjs will declare an entire package as deprecated if the latest version is marked as deprecated.

This is why debug@3.2.4 took over as latest when you published it after debug@4.0.0 and this is also why the entire debug package showed up as deprecated on the npmjs website after you deprecated debug@3.2.4 while it was tagged as latest. It only resolved itself once you manually reset the latest dist-tag back to 4.0.0, implicitly undeprecating the package.

Member Author

Qix- commented on `7fb104b` Sep 11, 2018

Wasn't clear you were referring to npm, hence:

Whatever is telling you 3.2.4 is latest is bugged

My apologies.

Please sign in to comment.