Migration

0.3.0 -> 0.4.0

Version 0.4.0 is an additive release centered on slug attributes and license snapshots. Existing integrations continue to work, but responses and webhook/JWT payloads include new optional fields.

What changed

  • Slugs now support attributes (JSON object) for license information such as gated features.
  • Generated licenses now store snapshotted slug attributes.
  • POST /generate responses now include attributes.
  • GET /management/licenses now returns license attributes.
  • GET/POST/PATCH /management/slugs now include slug attributes.
  • license.generated webhook payloads now include attributes.
  • Offline JWT tokens now include an attributes object claim from the license snapshot.
  • The management UI license details modal now supports runtime activation with fingerprint and optional activation metadata.

Required actions

  • Pull or rebuild the 0.4.0 Docker image.
  • No manual database migration is required for existing 0.3.0 installations; startup schema migration adds slug/license attributes columns.
  • No new environment variables are required.

Integration notes

  • If you consume /generate responses, handle the new optional attributes object.
  • If you consume /management/licenses or /management/slugs, update response parsing for attributes.
  • If you consume license.generated webhooks, update payload parsing for attributes.
  • If clients use offline JWTs for feature gating, read feature data from the nested attributes claim.
  • POST /activate metadata is activation-seat scoped, while POST /generate metadata remains license scoped.
  • The new UI activation action surfaces the full /activate response, including offline JWTs when the slug is offline-enabled.