Skip to main content

Changelog

Version 2.1.0 (Current)​

Status: Stable (additive to 2.0.2)

New Features​

  • Signed requests - APIs that need a fresh signature on every call (crypto exchanges) are described with a top-level SIGNING block of named recipes. A recipe combines a fixed set of building blocks: time, nonce, concat, hash, hmac, sign (Ed25519, RSA), JWT, encode and canonical parameter ordering.
  • request_signature SECURITY type - A method is signed only when its SECURITY names a recipe; SECURITY: [] is sent unsigned.
  • Mini-Wrekenfiles - HTTP.SIGNED: true marks a method the runtime signs.

Changes​

  • Headers and parameters a recipe produces (timestamp, nonce, signature, API key) are left out of HEADERS, INPUTS and DEFAULTS, and runtimes and AI consumers MUST NOT ask for them. This is an exception to the rule that every auth header references a DEFAULTS key.

Version 2.0.2​

Status: Stable (HTTP + SDK Unified)

New Features​

  • Unified HTTP + SDK execution - Single methods can now define both HTTP and SDK execution paths
  • Enhanced CLIENTS section - Explicit SDK client construction definitions
  • Improved AI safety - Stricter rules to prevent hallucination in LLM-driven code generation

Changes​

  • Updated core design principles to emphasize "no implicit inference"
  • Enhanced METHODS structure with hybrid execution support
  • Clarified relationship between full Wrekenfiles and mini-Wrekenfiles
  • Added comprehensive scope limitations documentation

Clarifications​

  • Auth header references - An auth header's value in HTTP.HEADERS is the name of a DEFAULTS key (e.g. Authorization: bearer_token, with bearer_token: "Bearer <TOKEN>"), never a literal credential. Runtimes substitute the real credential or omit the header.
  • Auth templates use Bearer - Templates use the standard Bearer scheme, not BEARER; many APIs reject the uppercase form.
  • Credentials outside headers - API keys sent in the query or a cookie are optional inputs with LOCATION: query / LOCATION: cookie. Cookie inputs are sent as Cookie header pairs, never in the URL.

Technical Improvements​

  • Deterministic code generation support
  • Enhanced support for language-agnostic specifications
  • Better separation of concerns in specification structure

Version 2.0.1​

Status: Previous stable version

Features​

  • Language-agnostic semantic specification
  • SDK and API unified description
  • LLM-optimized structure
  • Mini-Wrekenfile support
  • Comprehensive type system with external type documentation

Core Concepts​

  • SOURCES, UTILITIES, CONSTRUCTORS sections
  • Detailed METHODS structure
  • ERRORS and PAGINATION support
  • STRUCTS with external type documentation

Version 2.0.0​

Status: Initial stable release

Initial Features​

  • Basic Wreken spec
  • OpenAPI and SDK conversion support
  • Core YAML structure
  • Language-agnostic design principles
  • Basic documentation and examples