Releases and versioning
Understand Airlift package roles, independent version lines, and reproducible installation in CI.
Releases and versioning
Airlift publishes independently versioned npm packages. Install the CLI when you need the
fa command and install the SDK when you are building an application integration.
| Package | Purpose | Current version |
|---|---|---|
@fabricorg/airlift | Typed migration contracts, schemas, projections, and runtime composition | 0.17.0 |
@fabricorg/airlift-cli | The authenticated fa developer and automation command | 0.18.4 |
@fabricorg/airlift-adapter-adf | Credential-safe ADF/Synapse export import and target-artifact generation used by the CLI | 0.3.4 |
@fabricorg/airlift-adapter-lakebridge | Lakebridge workspace-job adapter seam | 0.2.0 |
@fabricorg/airlift-worker | Temporal worker and validation/cutover composition entry points | 0.15.0 |
Version independence
Package versions do not move in lockstep. Each CLI release pins the exact SDK and adapter generations it supports. Inspect a particular release before changing an automated environment:
npm view @fabricorg/airlift-cli@0.18.4 dependencies --json
npm ls @fabricorg/airlift @fabricorg/airlift-adapter-adfDo not infer compatibility from matching major or minor numbers.
Reproducible installation
Use exact versions for CI and unattended execution:
npm install --save-exact @fabricorg/airlift@0.17.0
npm install --save-dev --save-exact @fabricorg/airlift-cli@0.18.4
npx --yes --package @fabricorg/airlift-cli@0.18.4 fa versionBefore upgrading, read the command reference for removed or renamed commands and run your engagement automation against a non-production organization.
Verify package provenance
npm exposes the source and release commit metadata recorded during publication:
npm view @fabricorg/airlift-cli@0.18.4 repository gitHead --jsonFor a new release, require both fields and retain the resolved package integrity from the lockfile with your build evidence. A missing source or commit reference should block a regulated release until the package publisher supplies traceable metadata.