@pinta-ai/pinta-musecode 0.1.0 → 0.1.1
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 +22 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,27 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
-
## 0.1.
|
|
3
|
+
## 0.1.1
|
|
4
|
+
|
|
5
|
+
No code change. Cut so the catalog can ship a corrected manifest: published
|
|
6
|
+
manifests are immutable (`pinta-catalog` blocks in-place edits, because a
|
|
7
|
+
manager verifies the sha256 it already has), so the env-key fix needs a new
|
|
8
|
+
version to land on.
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
- The manifest template in `PUBLISHING.md` mapped `relay-endpoint` to
|
|
12
|
+
`OTEL_EXPORTER_OTLP_ENDPOINT`, and the catalog entry was copied from it.
|
|
13
|
+
`relay-endpoint` resolves to the **complete** traces URL, and that variable is
|
|
14
|
+
the non-signal *base* URL — an exporter appends the signal path to it and
|
|
15
|
+
posts to `/v1/traces/v1/traces`. The sidecar relay serves only
|
|
16
|
+
`POST /v1/traces`, so every span was dropped while enrollment reported
|
|
17
|
+
success and the hooks file looked correct. Measured by firing a real
|
|
18
|
+
`SessionStart` hook through each variable:
|
|
19
|
+
`OTEL_EXPORTER_OTLP_ENDPOINT` → `/v1/traces/v1/traces`,
|
|
20
|
+
`OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` → `/v1/traces`.
|
|
21
|
+
`README.md` already documented the `_TRACES_` form, so the two files
|
|
22
|
+
disagreed and the wrong one is what shipped.
|
|
23
|
+
|
|
24
|
+
## 0.1.0
|
|
4
25
|
|
|
5
26
|
Initial scaffold — stage 1 (observation) of the MuseCode adapter plan.
|
|
6
27
|
|