Skip to main content
ApiGlow v0.3.0
EN

Release notes, from day one.

One entry per release, taken from the app’s release notes. The live demo runs the released bundle, the same one the snippet on every page installs.

  1. 0.3.0

    2026-10-02
    • apiglow audit: the schema audit as a CI check — npx apiglow audit openapi.yaml fails the build on a finding of a given severity, a grade or a score under your bar
    • A committed baseline lets an existing API fail only on new findings, and a stale entry fails the run so it never hides a regression
    • Reports where reviewers look: SARIF for GitHub code scanning, annotations on the pull request, GitLab Code Quality, Markdown for the job summary, versioned JSON for scripts and agents — every finding at file:line:column
    • The apiglow/audit-action GitHub Action does it in one step, and the package ships an agent skill that audits, fixes and audits again
    • 137 audit rules in seven categories: the structure checked against the OpenAPI specification version by version, plus new security and agent readiness categories
    • Every finding says how to fix it; rules can be switched off or re-graded in an audit config block read by the page and the CLI alike; a broken file still gets a report, its syntax errors placed at their line
    • The audit loads only when someone opens it, and its page leads with the verdict
    • <Cards>, <Steps> and <Tabs> in prose pages, and apidoc:page/{slug} links between them — no MDX, nothing compiled
    • Enum values carry their meaning (x-enum-descriptions, x-enumDescriptions, or a oneOf of described constants)
    • A “Copy for AI” menu in the header on every page; endpoint pages read as a request and a response
    • Try-it fixes: headers and methods the browser refuses are named, server variables are filled in, relative URLs resolve against the schema, base64 secrets stay masked

  2. 0.2.0

    2026-08-16
    • Announcements: a strip above the documentation where you say what the schema cannot — a maintenance window, a deprecation date, a version that shipped
    • Declare announcements inline, or point announcements at a file your ops team edits with no redeploy of the host page; startsAt / endsAt publish and retire a notice on their own
    • The header holds one line at every screen size, phones included: theme, language, settings and About moved into a single preferences menu
    • Search is in the header at every width — an icon on a phone, a field from a tablet up
    • On a phone, the “Try it” button steps out of the way while you scroll down, and keyboard shortcuts are advertised only to devices that have a keyboard
    • The bottom credit bar is gone, and with it branding.footerLinks; About, with the license and third-party notices, lives in the header menu
    • Phone layout fixes: no sideways scroll from the spec selector, dialogs off the screen edges, navigation opening a new page at its top

  3. 0.1.0

    2026-08-15
    • Interactive documentation generated in the browser from OpenAPI 3.0.x–3.2.x — or Swagger 2.0, converted at load
    • Try-it console: schema-driven forms, environments with {{var}} interpolation and send-blocking, OAuth2 PKCE fully in-browser
    • Request history with replay; cURL, Postman v2.1, Markdown and HAR exports (secrets redacted by default) — and cURL/Postman/HAR import
    • Declarative scenarios with a “run all” report, a step-by-step tutorial mode, and Arazzo 1.1 import/export
    • In-browser schema audit: 38 rules, letter grade, Markdown report
    • Multi-spec with per-spec isolation; OpenAPI Overlay 1.1 applied at load; endpoint hiding
    • A reader can patch the schema locally with their own Overlay 1.1 document, and download it to send upstream
    • Prose pages resolve {{var}} from the reader’s environment; sensitive values render masked and are never emitted
    • An environment travels as a setup link — shared from the manager, or built from scratch without creating it
    • 35 daisyUI themes plus config-declared custom themes; English and French UI
    • llms.txt, llms-full.txt and MCP config generation — two OpenAPI→MCP bridges to pick from
    • One workflow, three readers: an authored scenario hands off as a generated GitHub Actions or GitLab CI job, secrets as names only
    • apiglow bake: static HTML and Markdown mirrors, a sitemap and a served llms.txt, from one author-side command