edf2csv 0.6.58 → 0.6.60
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/README.md +2 -0
- package/docs/CHANGELOG.md +24 -0
- package/package.json +1 -1
package/README.md
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,30 @@
|
|
|
3
3
|
Notable changes to edf2csv. Versions follow [semantic versioning](https://semver.org); while the
|
|
4
4
|
major version is 0, a minor bump may contain breaking changes.
|
|
5
5
|
|
|
6
|
+
## 0.6.60
|
|
7
|
+
|
|
8
|
+
### Changed: the publish step retries the two failures that are not the code's
|
|
9
|
+
|
|
10
|
+
Both failures seen while releasing were the registry's, not the tarball's. Publishing a batch
|
|
11
|
+
together made one run die on `E409 Conflict - Failed to save packument`, which is npm refusing a
|
|
12
|
+
write with another in flight. A later one died on `CA_CREATE_SIGNING_CERTIFICATE_ERROR - (403)
|
|
13
|
+
Forbidden`, which is Sigstore declining to mint the provenance certificate after a clean build
|
|
14
|
+
and a passing suite. Both published on a manual rerun, unchanged.
|
|
15
|
+
|
|
16
|
+
Three attempts with a widening pause, and the registry is asked between them: if the version is
|
|
17
|
+
already there, the write landed and whatever failed came after it, so the step succeeds rather
|
|
18
|
+
than retrying. That is what makes a retry safe here — it cannot publish the same version twice,
|
|
19
|
+
and it cannot mistake a genuine refusal for a transient one, because the check is what actually
|
|
20
|
+
shipped rather than what the exit code said.
|
|
21
|
+
|
|
22
|
+
## 0.6.59
|
|
23
|
+
|
|
24
|
+
### Added: an npm downloads badge on the README
|
|
25
|
+
|
|
26
|
+
`img.shields.io/npm/dt/edf2csv`, linked to the package page. It reads the registry's own download
|
|
27
|
+
total rather than a number written into the file, so it cannot drift the way the figures this
|
|
28
|
+
project keeps correcting have.
|
|
29
|
+
|
|
6
30
|
## 0.6.58
|
|
7
31
|
|
|
8
32
|
### Added: CI runs the six sweeps it has always claimed as its evidence
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.60",
|
|
4
4
|
"description": "Convert EDF, EDF+ and BDF biosignal recordings (European Data Format) to CSV from the command line. Local, streaming, and never resamples or alters units.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"edf",
|