edf2csv 0.6.60 → 0.6.62
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/docs/CHANGELOG.md +55 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,61 @@
|
|
|
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.62
|
|
7
|
+
|
|
8
|
+
### Changed: the homepage is real HTML, and a pasted link unfurls into something
|
|
9
|
+
|
|
10
|
+
Two findings from an SEO pass over the website, both the same shape: the site said less about
|
|
11
|
+
itself to machines than it does to people.
|
|
12
|
+
|
|
13
|
+
The documentation pages have been prerendered static HTML from the start, precisely so that
|
|
14
|
+
crawlers that do not run JavaScript — which is most of the AI crawlers the docs were written
|
|
15
|
+
for — get the full text. The landing page never got the same treatment: it was an empty
|
|
16
|
+
`<div id="root">` until the bundle arrived, so the one page that explains what the tool is was
|
|
17
|
+
blank to exactly the readers the prerendering exists for. It is now server-rendered at build
|
|
18
|
+
time through Vite's SSR transform and hydrated in the browser, and the build fails if the
|
|
19
|
+
rendered landing ever comes back as a stub, the same check the documentation pages have.
|
|
20
|
+
|
|
21
|
+
A pasted link had no image at all: `twitter:card` said `summary` and no `og:image` existed, so
|
|
22
|
+
Slack, iMessage and the rest unfurled the URL into two lines of grey text. There is now a
|
|
23
|
+
1200x630 card in the site's own oscilloscope idiom — the H1, the command, a trace — referenced
|
|
24
|
+
with `summary_large_image` from every page. One committed PNG rather than a per-page generator,
|
|
25
|
+
because eleven near-identical title cards would say less than one good one.
|
|
26
|
+
|
|
27
|
+
The smaller corrections follow the same principle. The sitemap dropped `<priority>`, which
|
|
28
|
+
Google states it ignores, for `<lastmod>` read from each page's commit history — and a page
|
|
29
|
+
whose date git cannot supply gets no tag, because a fabricated date teaches crawlers to
|
|
30
|
+
distrust all of them. The title now leads with the phrase people type ("Convert EDF to CSV
|
|
31
|
+
from the command line") while the H1 keeps the site's own voice. Documentation pages carry
|
|
32
|
+
BreadcrumbList and a `dateModified` from the same commit history; the SoftwareApplication
|
|
33
|
+
entity gained `sameAs` links tying the site, the repository and the npm package into one
|
|
34
|
+
thing, and a `softwareVersion` read from package.json at build. It still carries no
|
|
35
|
+
aggregateRating and no download count: the schema for star ratings is the one piece of SEO
|
|
36
|
+
this site will not do, because inventing social proof is fabricating data on a site whose
|
|
37
|
+
argument is that fabricating data is the problem.
|
|
38
|
+
|
|
39
|
+
Also fixed on the way through: the landing page never inlined the theme-restore script the
|
|
40
|
+
documentation pages have, so a reader who had chosen light mode got a flash of dark on every
|
|
41
|
+
visit to the homepage.
|
|
42
|
+
|
|
43
|
+
## 0.6.61
|
|
44
|
+
|
|
45
|
+
### Added: the pyEDFlib cross-check runs weekly instead of never
|
|
46
|
+
|
|
47
|
+
0.6.58 put six of the seven sweeps into CI and left this one out on purpose: it needs pyEDFlib
|
|
48
|
+
installed, and a check whose whole value is comparing against an independent implementation must
|
|
49
|
+
not quietly pass when that implementation fails to install. A green tick meaning "pip was
|
|
50
|
+
unhappy" is worse than no tick.
|
|
51
|
+
|
|
52
|
+
Its own scheduled workflow answers that. On a schedule a failed install is a failed run — there
|
|
53
|
+
is no pull request it would be blocking and no temptation to make it skippable — and weekly is
|
|
54
|
+
the right cadence for what it actually guards: drift in the arithmetic, or in pyEDFlib. Neither
|
|
55
|
+
moves at the speed of a commit. `workflow_dispatch` is there for running it against a change
|
|
56
|
+
that touches the scaler.
|
|
57
|
+
|
|
58
|
+
That is claim 1 on the correctness page — the one this project leads with — and it was the last
|
|
59
|
+
one whose evidence had to be produced by hand.
|
|
60
|
+
|
|
6
61
|
## 0.6.60
|
|
7
62
|
|
|
8
63
|
### Changed: the publish step retries the two failures that are not the code's
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.62",
|
|
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",
|