@pinta-ai/pinta-opencode 0.3.1 → 0.5.0

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 CHANGED
@@ -1,5 +1,31 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.4.0
4
+
5
+ - Consolidate the duplicated low-level utilities (`guard`, `otlp`, `redact`,
6
+ `transport`, `trace`) into the shared private package `@pinta-ai/core`. `src/core/*`
7
+ is now a thin opencode-specific binding layer: the plugin keeps its 50ms
8
+ fail-open guard default, its `pinta-opencode/<version>` User-Agent, explicit
9
+ (non-`process.env`) options, and core's **in-memory** retry queue +
10
+ `MemorySessionTraceManager`, since it is a long-lived in-process plugin.
11
+ - `@pinta-ai/core` is a devDependency, bundled into `dist/plugin.js` by esbuild at
12
+ build time, so npmjs consumers never need private-registry access.
13
+ - Bump `@pinta-ai/core` `^0.2.0` → `^0.3.0`. The upgrade is additive; no adapter
14
+ source change was needed. Tool spans now carry `pinta.client.rtt_ms` /
15
+ `pinta.client.op` for free: the plugin already forwards its guard result
16
+ through `telemetry.toolBefore` → `buildOtlpPayload` → core's `buildPayload`,
17
+ and core `0.3.0` derives the client-call timing from the
18
+ `GuardResult.clientRttMs` it now measures. The manager can only time its own
19
+ handler, so `clientRttMs - durationMs` gives it the transport overhead.
20
+ - Fix `package-lock.json`, which resolved `@pinta-ai/core` as a local link to
21
+ `../pinta-core` (a dev-machine-only path) and recorded it as a runtime
22
+ dependency. It now resolves from GitHub Packages with an integrity hash, as a
23
+ devDependency, so `npm ci` works in CI.
24
+ - Restore npm OIDC trusted publishing in the publish workflow (the committed
25
+ `.npmrc` pointed npmjs auth at a nonexistent `NPM_TOKEN` secret, which would
26
+ have failed `npm publish` with ENEEDAUTH), and pin npm to `11.18.0` (npm 12.x
27
+ requires node >=22.22, but the job runs node 20).
28
+
3
29
  ## 0.2.1
4
30
 
5
31
  - Fix `package-lock.json` so CI `npm ci` resolves (regenerated with a full