Updates and migrations

Before updating

Installed blocks are files in your project. CoBlick does not replace them in the background.

• Commit your current changes.
• Read the block's current release note.
• Note the routes, data, and actions you changed after installation.

Review the difference

Run the current install command with --diff. This shows how the catalog version differs from the files in your app.

Review the main block file first, then shared UI files. A shared UI change can affect screens that do not use this block directly.

Apply the update

1. 1
   Bring in the changes you need

   Keep your application data, routes, permissions, and copy.

2. 2
   Run the screen

   Exercise the main task and each state changed by the update.

3. 3
   Run project checks

   Use the typecheck, tests, and production build already used by your app.

4. 4
   Commit separately

   A focused update commit makes later review and rollback easier.

Replaced blocks

If a release is withdrawn, its block page explains the reason and links a replacement when one exists. Files already committed to your app remain yours.

Review the replacement as a new block. Do not overwrite a working screen until you have compared its files and completed the same application checks.