[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@cloudflare/flagship@0.7.0

Minor Changes

• #50 f4ef40e Thanks @akshitsinha! - FlagshipClientProvider now evaluates every flag in a single OFREP bulk request on initialize() and on every context change, so prefetchFlags is no longer needed and is ignored. Cached results keep their evaluation reason instead of CACHED, and per-flag failures surface their OpenFeature error code. The new pollInterval option re-evaluates flags in the background and emits PROVIDER_CONFIGURATION_CHANGED when results change.

• #49 0d46808 Thanks @akshitsinha! - Report provider state accurately. Local-evaluation server providers emit PROVIDER_STALE when a definitions refresh fails and PROVIDER_READY when it recovers, and fail initialization with PROVIDER_FATAL on a 401 or 403. The client provider now rejects initialize() and onContextChange() when every flag fetch fails, instead of reporting READY, and onClose() now discards a load that is still in flight.

Patch Changes

• #48 c6c6864 Thanks @akshitsinha! - Map the OpenFeature errorCode from Flagship HTTP error responses, so INVALID_CONTEXT, PARSE_ERROR and TYPE_MISMATCH are no longer reported as GENERAL.

@cloudflare/flagship-go@0.7.0

@cloudflare/flagship-python@0.7.0

[akshitsinha]

/bonk review this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@cloudflare/flagship@52

commit: 5560d8a

[ask-bonk]

LGTM!

I checked the PR as a mechanical Changesets release: it bumps all three SDKs to 0.7.0 and consumes the three pending changesets.

• Versions: package.json (TypeScript, Python, Go), pyproject.toml and the cloudflare-flagship entry in uv.lock all say 0.7.0.
• Changelogs: the TypeScript CHANGELOG.md gets one 0.7.0 section matching the PR body. The Go and Python changelogs only get their heading bumped, as expected for private SDK packages.
• Changesets: the three deleted files are the ones that produced the 0.7.0 entries.
• Lockfile: uv.lock also moves its revision field from 3 to 5, because the release workflow's uv is newer than the one that last wrote it. It is harmless and no change is needed, since setup-uv is unpinned and installs the latest uv. I couldn't run uv here, because it isn't installed.

github run