unstale

npm / @configcat/sdk

@configcat/sdk

What changed in @configcat/sdk 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.

1 breaking2 deprecations4 behavior and defaults3 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.0 on npm

@configcat/sdk 110 changes

Breaking changes 1

  • FetchRequest.url no longer includes query string parameters and contains only the path to the config JSON file; the SDK identifier string can be read from the User-Agent header.

    1.1.0release notes

Deprecations 2

  • The Node.js and Bun option is deprecated; use httpAgentFactory instead.

    1.1.0release notes

  • The Node.js and Bun option is deprecated; use httpsAgentFactory instead.

    1.1.0release notes

Behavior and default changes 4

  • Built-in config fetchers add debug logging, and logging is enabled for these fetchers even when they are created externally.

    1.1.0release notes

  • Disposing a config fetcher during an in-progress fetch aborts the fetch operation, including pending HTTP requests.

    1.1.0release notes

  • Failed HTTP requests are retried once after an unexpected status code, timeout, or request error, which can reduce HTTP errors and timeouts.

    1.1.0release notes

  • For Node.js and Bun, NodeHttpConfigFetcher now creates and manages its own internal agent instances instead of using http.globalAgent and https.globalAgent.

    1.1.0release notes

Fixes and other changes 3

  • The CF-RAY header is also logged when response headers arrive but downloading the response body times out or fails.

    1.1.0release notes

  • Fixes a bug that could crash some runtimes, including Node.js or Deno, when an error was left unhandled during cache sync or config refresh.

    1.1.0release notes

  • URL processing and manipulation now properly handle user-provided base URLs or fetch request URLs containing query strings or URI-encoded characters.

    1.1.0release notes