@_linked/server 2.13.4 → 2.13.5
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 +18 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,23 @@
|
|
|
1
1
|
# @\_linked/server
|
|
2
2
|
|
|
3
|
+
## 2.13.5
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- [#92](https://github.com/linked-fw/server/pull/92) [`c17a450`](https://github.com/linked-fw/server/commit/c17a4501f55b824ad3f22ab24fc989f8145f11e7) Thanks [@flyon](https://github.com/flyon)! - Cover `GET /resized/*` with an SVG source.
|
|
8
|
+
|
|
9
|
+
The route had no test at all. These assert on the BYTES and the KEY rather than
|
|
10
|
+
the status code, because the half that matters is silent: writing PNG bytes under
|
|
11
|
+
a `.svg` key still returns 200, and only misbehaves on the next request, when the
|
|
12
|
+
cache-hit path types the response `image/svg+xml` from that extension.
|
|
13
|
+
|
|
14
|
+
Both branches are covered — the `src`-parameter branch and the uploads branch —
|
|
15
|
+
because the bug was in both, for two different reasons. A third case pins a JPEG
|
|
16
|
+
source as staying a JPEG, so the rasterization cannot quietly become
|
|
17
|
+
unconditional.
|
|
18
|
+
|
|
19
|
+
Verified against the reverted fix: both SVG cases fail, the JPEG case passes.
|
|
20
|
+
|
|
3
21
|
## 2.13.4
|
|
4
22
|
|
|
5
23
|
### Patch Changes
|