Tags

Tags give the ability to mark specific points in history as being important

  • v0.2.2

    87c713a6 · fix: preserve multi-type schemas during Surge regeneration · 
    v0.2.2

- Fixed generation for schema type lists containing several non-null primitives, including nullable call-flow metadata. The patch preserves each branch as an anyOf union instead of rejecting the specification.
- Regenerated the client with call-flow-created webhook models and union helpers.

  • v0.2.1

    00767959 · v0.2.1: add created_at to messages and message events · 
    v0.2.1

- Added `Message.CreatedAt` (`*time.Time`), the time the message was added to the conversation. It is null for scheduled messages until they are created. For imported messages it is the original creation time.
- Added a `CreatedAt` field (`time.Time`) to the `Data` payload of `MessageDeliveredEvent`, `MessageFailedEvent`, `MessageReceivedEvent` and `MessageSentEvent`.
- Updated the example payloads in the doc comments of `Message`, `MessageList`, `LinkFollowedEvent` and the four message events to include `created_at`.

  • v0.2.0

    b71ebfcf · v0.2.0: generate from the spec Surge's API publishes · 
    v0.2.0

- The client is generated from the spec Surge's API publishes at `https://api.surge.app/openapi.json`. The Stainless-hosted copy of the spec it used before is no longer publicly readable, so scheduled regeneration had stopped.
- Added the four toll-free campaign operations and their models. Nothing was removed.
- Updated Semgrep in the development image to 1.182.1 and refreshed its locked dependencies. certifi 2026.10.23 drops the emSign root CAs whose intermediate keys were compromised (GHSA-6q48-6c7w-9gw2).
- Dependabot no longer opens pull requests for `mcp` or the OpenTelemetry packages in `requirements-semgrep.txt`. Semgrep pins their versions itself, so bumping one of them on its own cannot install.
- Updated kin-openapi, which the code generator uses, from 0.142.0 to 0.149.0. The newer version fixes several panics on malformed specs reported in GitHub security advisories.
- The security scan merges its two gitleaks runs into one SARIF run. GitHub code scanning rejects a report with two runs from the same tool, so no scan results had been uploaded.

  • v0.1.2

    bd57447d · v0.1.2: build the dev image on Debian and require Go 1.26.10 · 
    v0.1.2

- The development image is based on Debian (`golang:1.26.10-trixie`) instead of Alpine. Alpine keeps only the latest build of each package, so the exact pins broke the image build whenever a package was updated. System packages now come from the snapshot.debian.org date the base image was built from, which keeps them fixed for a given base image digest. jq 1.8.2, shellcheck 0.11.0 and shfmt 3.13.1 keep their versions, and Semgrep runs in its own virtual environment.
- Raised the minimum Go version in `go.mod` from 1.26.9 to 1.26.10, which fixes the `crypto/x509` vulnerability GO-2026-6809 found by govulncheck.
- The issue-pull workflow runs at hours derived from the repository name instead of the same four hours as every other repository.

  • v0.1.1

    2f07410f · docs: show how to look up the full API in the skill and README · 
    v0.1.1

- Documentation only. The agent skill explains how to look up every endpoint, parameter and model with `go doc` or on pkg.go.dev, and declares its license.
- The skill no longer lists the API credentials under OpenClaw's `requires.env`, which kept OpenClaw from loading it until they were set. It requires only `go`; the credentials are still documented as what your program reads.
- The README points to the full API reference, and the examples in the README and the skill were checked against the current code.

  • v0.1.0

    c0ad6a0e · v0.1.0: go-surge client generated from the official OpenAPI spec · 
    v0.1.0

- Added `surge`, a REST client generated with oapi-codegen from Surge's public OpenAPI document (spec version 1.0, OpenAPI 3.1.1). It covers all 41 operations across 25 paths, including accounts, audiences, blasts, campaigns, contacts, messages, phone numbers, recordings, users, tokens and verifications.
- Number fields are `float64` instead of oapi-codegen's default `float32`. All component schemas are retained, including webhook payload models.
- `make generate` reads the current Stainless spec URL from `https://raw.githubusercontent.com/surgeapi/python-sdk/main/.stats.yml`, downloads it, downconverts nullable type lists, constants and schema examples for oapi-codegen, and regenerates the client. The initial source is `https://storage.googleapis.com/stainless-sdk-openapi-specs/surge/surge-ffd563fe3318efc4a305510ec4ae66fea4a32d96ed34abd985b44692edb3535e.yml`. The spec is not committed.