Skip to content
NanoFlags
Start free

Changelog

What shipped,and when.

Dated entries, newest first, written from our release history. We list only what is live, and never backdate.

@nanoflags/sdk on npm (opens in a new tab)Status

November 2026

    1. Integrations

      GitHub App: flag states in pull requests

      • Install the NanoFlags GitHub App and link a repository to a project from the dashboard.
      • Pushes update code references, so each flag page shows where the flag is used in your code.
      • Pull requests get one comment, kept up to date, with the states of the flags they touch.
      • A "NanoFlags scenarios" check runs your saved scenarios on each pull request (Team plan and above).
      • Flag pages hint at flags that look stale, so you can clean them up.
      Read more

    1. Operations

      Hourly backups and public incidents

      • Backups now run every hour instead of nightly, and are kept for 30 days in separate storage.
      • We are alerted when the newest backup is more than three hours old.
      • The status page lists incidents and planned maintenance, with updates until they are resolved, and keeps 90 days of history.
      • Services are checked every 5 minutes, with alerts on failure and recovery.
      Read more
    2. DashboardCLI@nanoflags/cli 0.2.0

      Stricter scenario evidence, promotion records and CLI 0.2.0

      • Scenario runs by the change's author or its draft editors no longer satisfy a required scenario check: someone else has to run them.
      • Promoting a change from Staging to Production now leaves a record.
      • Scenarios are now versioned.
      • Restoring a revision to a draft now restores its segments too.
      • CLI 0.2.0 adds nanoflags flags create.
      • A setup checklist and a step-by-step quickstart in the dashboard.
      Read more
    3. SDKSecurity@nanoflags/sdk 0.4.0

      SDK 0.4.0 verifies signatures by default

      • SDK 0.4.0 verifies the Ed25519 signature of every configuration bundle by default when it talks to the official edge.
      • Signing keys can be rotated: the public key list is at edge.nanoflags.io/v1/keys.
      • Bundles carry the evaluation engine version, and an SDK refuses a bundle it doesn't understand.
      • Browser keys now receive only the segments their client-exposed flags use.
      • Deleting an environment removes its configuration from the edge.
      Read more
    4. SecurityDashboard

      Security hardening

      • The database itself now refuses an approval from the change's own author.
      • Flag values are validated against their JSON Schema before they can be saved.
      • Two-step sign-in is enforced on the server, with recovery codes.
      • Plan limits are enforced in the database, and only an owner can relax a protected environment's publishing policy.
      • Invitations need the invitee's consent and arrive by e-mail; more actions are recorded in the audit log.
      • Test sessions are off in Production.
      • The status page shows only real, live checks. Global search (Cmd/Ctrl+K) in the dashboard.
      Read more
    5. SDK@nanoflags/sdk@nanoflags/cli@nanoflags/openfeature-provider

      Client packages are public and on npm

      • The SDK, CLI and OpenFeature provider are published to npm from a public repository.
      • They are licensed Apache-2.0. The dashboard, edge and backend stay proprietary.
      • The GitHub Action lives in the same public repository.
      Read more (opens in a new tab)

    1. Launch

      NanoFlags launches on nanoflags.io

      • The dashboard and edge API are live: flags, segments, environments, drafts, change requests with approvals, scenarios, revisions and restore.
      • Every publish produces a signed bundle that reaches connected SDKs over WebSockets.
      • Propagation is measured every 5 minutes from several regions and published on the status page.
      • Paid plans through Paddle, our merchant of record, with a 14-day refund.
      • Documentation in English, and a guide in Arabic.
      Read more