stacklift.yaml
The project configuration file. The CLI finds it by walking up from the working directory, like git finds .git. It is validated with the same zod schema the CLI ships.
yaml
version: 1
project:
org: acme # organization slug
project: acme-mobile
stack: react-native # adapter id
appIdentifier: com.acme.mobile
platforms: [android, ios]
runtimeVersion: 1.0.0
defaultChannel: staging
stores: # optional; synced on `release create`
ios: https://apps.apple.com/us/app/my-app/id1234567890
android: https://play.google.com/store/apps/details?id=com.acme.app
build:
command: npm run bundle # informational; Stacklift does not run it
artifacts:
- { platform: android, kind: js-bundle, path: dist/android.zip }
- { platform: ios, kind: js-bundle, path: dist/ios.zip }
rollout:
percentage: 100
autoExpand: false # explicit opt-in only
steps: [5, 25, 50, 100]
intervalMinutes: 120
maxFailureRate: 0.05| Field | Notes |
|---|---|
version | Always 1 |
project.org, project.project | Slugs or ids. --org / --project override them |
stack | One of the adapter ids from GET /api/v1/adapters |
platforms | Must be supported by the stack |
runtimeVersion | Compatibility key; required to create a release (here or via flag) |
defaultChannel | Used by deploy and release create --deploy |
stores.* | Store listing links per platform (ios, android, macos, windows, linux). https and the store's own host only. Synced to the project on release create (needs project:update; skipped otherwise) |
build.artifacts | Used by release create when no --artifact is passed. Paths are relative to the file |
rollout.* | Defaults for staged rollouts. autoExpand needs intervalMinutes |
Run stacklift doctor to validate the file against the adapter.