Skip to content

Releases: Tsvihun/HyperProxySwift

HyperProxySwift 0.5.0

Choose a tag to compare

@Tsvihun Tsvihun released this 04 Oct 06:03

HyperProxySwift 0.5.0 updates the provider snapshot and makes Swift integrations clearer.

  • Refresh official provider schemas on 2026-10-03: 2,342 routes, 18,272 generated
    models and 2,099 typed operation bindings. Add OpenRouter batches/end users/private
    endpoints, Mistral managed indexes and pipeline configuration, ElevenLabs agent
    merge proposals/flow templates, Together deployment revisions and BFL FLUX.3 images.

  • Follow upstream removals and path changes: OpenAI eval cancellation moves to /cancel,
    Gemini environment file download drops filesId, Mistral removes campaign/explorer
    operations and consolidates connector credentials, BFL removes finetuned fill, and
    DeepL removes quality submission and pluralizes its polling path. Removed generated
    helpers and changed path arguments require migration for callers using them.

  • Update reviewed DeepSeek models for deepseek-flash, Pro Responses support, image
    tool outputs, inline file data, model-discovery metadata, cache details and aborted
    completion reasons. The former Flash enum cases and Responses web-search cases are
    removed; content text is optional and tool output now accepts a string/parts union.

  • Match updated OpenAI binary/JSON/text/SSE response contracts, fix OpenRouter boolean
    literal streaming bindings, and update BFL's async submission allowlist. Renew source
    and artifact inventory hashes; renew the recorded release review for this snapshot.

  • Add semantic request aliases, message factories, enum convenience values and
    catalog-bound provider services. Manual service initialization now throws when
    the supplied provider or operation set is invalid.

  • Serialize App Attest enrollment/reset state and save cached state only after
    persistent storage succeeds. Give each WebSocket one reader, reject concurrent
    consumers and preserve messages between consecutive single-message receives.

  • Tighten realtime audio lifecycle and cancellation, handle split PCM16 samples,
    and consistently format handwritten Swift code.

  • Rewrite README and integration guides, validate
    every Swift documentation example in CI and make QuickStart configuration explicit.

Installation

Use Swift Package Manager with .upToNextMinor(from: "0.5.0"), or select only the provider product you need. CocoaPods uses the matching 0.5.0 component graph from the Git tag; see the current installation instructions.

CocoaPods registry status: Trunk publication is incomplete. Its API timed out after committing Brave, Replicate and Stability specifications to the Specs repository, and subsequent attempts return HTTP 500 while their version indexes remain on 0.4.1. The aggregate is not published in Trunk. Use SwiftPM or specify the Git tag for every CocoaPods component; a bare ~> 0.5.0 installation is not yet supported for the complete graph.

Validation

  • 153 SDK tests passed.
  • README and all Swift guide examples typechecked (64 blocks); the website examples were checked with them (70 total).
  • QuickStart built; missing/invalid configuration exits without provider requests.
  • Aggregate and component CocoaPods specifications passed iOS build validation.
  • Generated catalog, provider modules, models and gateway contract reproduced from the pinned inputs; 29 generator tests passed.
  • Release provenance gate passed. Source risk acceptances were explicitly renewed by the maintainer; no unverified upstream licence is claimed.

The catalog is the reviewed 2026-10-03 snapshot, not live provider conformance. Provider account access and physical-device attestation remain integration checks.

HyperProxySwift 0.4.1

Choose a tag to compare

@Tsvihun Tsvihun released this 19 Sep 21:17

Patch release with complete source-provenance records and matching SwiftPM/CocoaPods version metadata.

  • Records exact URLs and SHA-256 hashes for all 25 generated provider source snapshots.
  • Preserves required OpenAI and Brave MIT notices.
  • Distinguishes evidence-backed approvals from explicit maintainer risk acceptances.
  • Keeps runtime and public Swift APIs unchanged from 0.4.0.

Validated locally with the release provenance gate, 138 Swift tests, source-layout checks, documentation example typechecking, Quick Start build, and the complete CocoaPods aggregate lint.

HyperProxySwift 0.4.0

Choose a tag to compare

@Tsvihun Tsvihun released this 19 Sep 19:18

HyperProxySwift 0.4.0 expands the typed provider SDK across 18 provider families.

Highlights:

  • 2,292 provider routes, 17,559 generated models, and 2,036 typed operation bindings.
  • Exhaustive Swift enums for closed provider value sets and custom(...) only for explicitly open schemas.
  • Typed gateway rejection errors and safer retry behavior.
  • Compatible legacy-gateway migration transport, including HTTP and gRPC metadata.
  • Updated security, streaming, multipart, polling, WebSocket, and observability behavior.
  • Swift Package Manager and 22 aligned CocoaPods specifications at version 0.4.0.

The generated-source rights review remains open; see Compliance/README.md in the tagged source for provenance status.

HyperProxySwift 0.3.0

Choose a tag to compare

@Tsvihun Tsvihun released this 05 Sep 18:05

Changelog

0.3.0

  • Select a preset revision or environment and encode typed JSON prompt variables with
    HyperProxyPrompt; read the served revision from response metadata.
  • Attach validated session metadata and custom properties using HyperProxyTrace.
  • Encode metrics-only events for analytics without a gateway. A trusted macOS process can
    submit them with HyperProxyTelemetryClient; mobile apps relay through their own backend.
  • Prevent direct provider requests from leaking HyperProxy/AIProxy control headers,
    credentials, prompt variables, trace labels or HyperProxy attestation headers.
  • Keep repeated prompt/trace configuration deterministic and clear stale selectors.
  • Extend the Quick Start and document credential boundaries, deduplication and retry ownership.

No new third-party dependencies. Existing provider-native operations and gateway routing APIs
remain source-compatible. Telemetry submission is explicit; no automatic instrumentation or
durable queue is installed.