@ryuu-64/dsh-find-all 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +20 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,25 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.2
|
|
4
|
+
|
|
5
|
+
Nothing about the code changed — this release exists only because **0.1.1 can never be
|
|
6
|
+
published**. The publish that produced `+ @ryuu-64/dsh-find-all@0.1.1` left the version in npm's
|
|
7
|
+
staging area rather than on the registry, and the registry refuses to reuse the coordinate:
|
|
8
|
+
|
|
9
|
+
```text
|
|
10
|
+
409 Cannot publish over previously staged version "0.1.1"
|
|
11
|
+
409 Cannot stage previously published version "0.1.1"
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
That is expected, not a bug: registry data is immutable, and *"if you've ever published a package
|
|
15
|
+
called bob at version 1.1.0, no other package can ever be published with that name at that
|
|
16
|
+
version. This is true even if that package is unpublished"* ([npm Unpublish
|
|
17
|
+
Policy](https://docs.npmjs.com/policies/unpublish)). The 0.1.1 tarball never became reachable
|
|
18
|
+
(`/0.1.1` → 404, its tarball → 404), so the fix is republished unchanged as 0.1.2.
|
|
19
|
+
|
|
20
|
+
The 0.1.1 section below still describes this release's content: same bundle, same fix, byte for
|
|
21
|
+
byte.
|
|
22
|
+
|
|
3
23
|
## 0.1.1
|
|
4
24
|
|
|
5
25
|
### Fixed
|
package/package.json
CHANGED