GNL

Changelog

Every release, newest first. The @gnldev/* packages are versioned and released together, so one version number covers all of them.

Each summary says what changed and, for a minor, why it is one — in 0.x a minor is where a breaking change goes. The full entry, with every change and its reason, is in CHANGELOG.md.

The full changelog on GitHub →RSS feed

  1. 0.8.0

    A misspelled Principal field or error-code name is now a compile error, and every package declares sideEffects, so bundlers drop what an app does not use — the durable core went from 61.5 to 57.4 KiB gzip. Type changes only; nothing changes at runtime.

    Full entry →
  2. 0.7.0

    End users are isolated by default, at one point, for free, and every package asks who the caller is the same way (identify). Many entries are breaking — read the upgrade list at the top of the entry first.

    Full entry →
  3. 0.6.0

    McpServer.listTools is now async and takes the caller, and Studio no longer starts on a non-loopback host when its only credentials are the development ones.

    Full entry →
  4. 0.5.0

    Validation tightened in three places — the runId record separator, JWT nbf and the tool test form — and StudioAgentRunner gained a fourth parameter.

    Full entry →
  5. 0.4.1

    A guard's warning overstated what it did. The message changed; the behaviour did not.

    Full entry →
  6. 0.4.0

    Two ways a delete could take somebody else's data, most of all with ids that contain a colon. A ^0.3.0 range does not pick this up on its own — upgrade deliberately.

    Full entry →
  7. 0.3.0

    A thread id could rename its own keyspace, and one sweep then deleted every thread. Two words that used to be accepted are now refused.

    Full entry →
  8. 0.2.0

    One change to a persisted key schema — read Changed before upgrading.

    Full entry →
  9. 0.1.0

    The first release on npm.

    Full entry →