v1 latest

Versioning

Flagify is composed of independent components — each with its own release cycle and version number. This page explains how versioning works across the project.

Components

Component Package Current version Changelog
CLI @flagify/cli v1.1.0 GitHub
Node SDK @flagify/node v1.0.7 GitHub
React SDK @flagify/react v1.0.7 GitHub
NestJS SDK @flagify/nestjs v1.0.7 GitHub
Astro SDK @flagify/astro v1.0.7 GitHub

Independent versioning

The CLI and JavaScript SDKs live in separate repositories and follow their own release cadence:

  • CLI (flagifyhq/cli) — Released when CLI features, commands, or bug fixes ship.
  • JavaScript SDKs (flagifyhq/javascript) — Released when SDK packages change. All four SDK packages (node, react, nestjs, astro) share the same version number within a release.

A version bump in one component does not require a bump in the other — the CLI and SDKs advance independently whenever one of them has changes to ship.

Compatibility

All Flagify components communicate through the Flagify API. As long as you are using a v1.x.x version of any component, they are compatible with each other.

CLISDKsAPICompatible
v1.x.xv1.x.xv1Yes

Semantic versioning

All Flagify packages follow Semantic Versioning:

  • Patch (1.0.x) — Bug fixes, no breaking changes.
  • Minor (1.x.0) — New features, backwards compatible.
  • Major (x.0.0) — Breaking changes. Migration guide provided.

Checking your versions

CLI:

flagify version

Node SDK:

npm list @flagify/node

React SDK:

npm list @flagify/react

Staying up to date

CLI:

npm update -g @flagify/cli
brew upgrade flagify

SDKs:

npm update @flagify/node @flagify/react