funoteka 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 +16 -0
- package/DEPLOY.md +2 -2
- package/dist/api/envelope.js +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -9,6 +9,22 @@ The version lives in exactly one place — `package.json`.
|
|
|
9
9
|
|
|
10
10
|
_(nothing yet)_
|
|
11
11
|
|
|
12
|
+
## [0.1.2] — 2026-09-17
|
|
13
|
+
|
|
14
|
+
### Fixed
|
|
15
|
+
|
|
16
|
+
- **The version the server reports is now the version it is.** `0.1.1`'s image and
|
|
17
|
+
package both answered `0.1.0` on `/health` and in every Subsonic envelope,
|
|
18
|
+
because the version lives in a constant (`SERVER_VERSION`) that a test pins to
|
|
19
|
+
`package.json` — and the bump to `0.1.1` raised the manifest and left the
|
|
20
|
+
constant behind. **That test failed, and `0.1.1` was tagged while CI was red**,
|
|
21
|
+
which is the more serious half of this: the pipeline was watching the artefacts
|
|
22
|
+
and nobody was watching the pipeline. The constant is corrected, and the release
|
|
23
|
+
job now fails when the image it pulls answers with a version other than the one
|
|
24
|
+
the release is about — a check that can fail is what would have caught it.
|
|
25
|
+
- Nothing else changed: the same program as `0.1.0` and `0.1.1`, and the same
|
|
26
|
+
schema.
|
|
27
|
+
|
|
12
28
|
## [0.1.1] — 2026-09-17
|
|
13
29
|
|
|
14
30
|
### Fixed
|
package/DEPLOY.md
CHANGED
|
@@ -61,7 +61,7 @@ node -e "console.log(require('crypto').randomBytes(32).toString('base64url'))"
|
|
|
61
61
|
## 3. Path A — Docker (main path)
|
|
62
62
|
|
|
63
63
|
Works the same on a laptop, a NAS and a VDS. There is a **published image** —
|
|
64
|
-
`ghcr.io/kzntsv-dev/funoteka:0.1.
|
|
64
|
+
`ghcr.io/kzntsv-dev/funoteka:0.1.2`, `linux/amd64` and `linux/arm64` in one
|
|
65
65
|
manifest — and `build: .` still builds on the machine that runs it (that is the
|
|
66
66
|
path where a published image is not wanted or not reachable).
|
|
67
67
|
|
|
@@ -75,7 +75,7 @@ docker run -d --name funoteka -p 4533:4533 -p 4534:4534 \
|
|
|
75
75
|
-e FUNOTEKA_ADMIN_TOKEN=<the token you generated> \
|
|
76
76
|
-e FUNOTEKA_SUPERVISED=1 -e FUNOTEKA_LOG_FILE=/data/funoteka.log \
|
|
77
77
|
-v "$MUSIC":/music:ro -v funoteka-data:/data \
|
|
78
|
-
--restart unless-stopped ghcr.io/kzntsv-dev/funoteka:0.1.
|
|
78
|
+
--restart unless-stopped ghcr.io/kzntsv-dev/funoteka:0.1.2
|
|
79
79
|
```
|
|
80
80
|
|
|
81
81
|
`FUNOTEKA_SUPERVISED=1` is what makes `POST /restart` a restart rather than a
|
package/dist/api/envelope.js
CHANGED
|
@@ -30,7 +30,7 @@ export const API_VERSION = '1.16.1';
|
|
|
30
30
|
* module every route depends on.
|
|
31
31
|
*/
|
|
32
32
|
export const SERVER_TYPE = 'funoteka';
|
|
33
|
-
export const SERVER_VERSION = '0.1.
|
|
33
|
+
export const SERVER_VERSION = '0.1.2';
|
|
34
34
|
/**
|
|
35
35
|
* The fields every answer carries, whatever the answer is.
|
|
36
36
|
*
|