⌘K

Deploy to Production

Tag a frame deployment and manage its rollout from the Dashboard.

When a frame is ready to ship, deploy it with a tag. Tags are what the Dashboard tracks for release management, percentage rollouts, and rollbacks.

Deploy with a tag

nativeblocks frame deploy -f ./frames/home.ts --tag v1.2.0

The frame is uploaded and a new tagged version is created. It is not yet active. Users still see the previously active version.

Activate in the Studio

Go to the Studio and open your frame's release management panel. From there you can:

  • Set Direct release for the new tag to make it live for all users
  • Set a percentage release to gradually release to a subset of users
  • Set a conditional release to deliver the frame to a subset of users
  • Roll back to any previous tag with one click

Tagging strategy

Use a consistent versioning scheme that matches your app releases. Some teams align CLI tags with their app version codes, others use independent semantic versions.

# Align with app version
nativeblocks frame deploy -f ./frames/home.ts --tag v2.5.0

# Independent frame versioning
nativeblocks frame deploy -f ./frames/home.ts --tag home-v3

Deploy multiple frames

Deploy each frame separately. You can tag them all with the same version string to group them as a release:

nativeblocks frame deploy -f ./frames/home.ts --tag v1.2.0
nativeblocks frame deploy -f ./frames/profile.ts --tag v1.2.0
nativeblocks frame deploy -f ./frames/checkout.ts --tag v1.2.0

What's next