Merge branch 'main' of https://github.com/TobikoData/sqlmesh

Author: sungchun12

.circleci/continue_config.yml

@@ -172,7 +172,7 @@ jobs:
 
   ui_test:
     docker:
-      - image: mcr.microsoft.com/playwright:v1.53.2-jammy
+      - image: mcr.microsoft.com/playwright:v1.54.1-jammy
     resource_class: medium
     steps:
       - halt_unless_client

.pre-commit-config.yaml

@@ -23,3 +23,8 @@ repos:
         files: *files
         require_serial: true
         exclude: ^(tests/fixtures)
+      - id: valid migrations
+        name: valid migrations
+        entry: tooling/validating_migration_numbers.sh
+        language: system
+        pass_filenames: false

docs/cloud/features/upgrade/upgrade-ui-available.png

@@ -0,0 +1,75 @@
+# Upgrading Tobiko Cloud
+
+Tobiko regularly releases new versions of Tobiko Cloud that add features and improve reliability.
+
+This page describes how to upgrade your Tobiko Cloud projects to a newer version.
+
+## Upgrade availability
+
+Navigate to `Settings > Upgrade` in the Tobiko Cloud UI to determine whether a new version of Tobiko Cloud is available for your project.
+
+If your project is already up to date, you will see a grey message:
+
+![Tobiko Cloud Upgrade Already Up-to-Date](./upgrade/upgrade-ui-up-to-date.png)
+
+If a new version is available for your project, the page will include a notification box, version, and blue Upgrade Now button:
+
+![Tobiko Cloud Upgrade Page](./upgrade/upgrade-ui-available.png)
+
+## Upgrading a project
+
+On the Upgrade page, you can choose to upgrade to the latest version or specify a custom version.
+
+!!! info "Upgrade Permissions"
+    Only users with Tobiko Cloud `Admin` permissions can perform upgrades.
+
+!!! danger "Upgrade Side Effects"
+    The upgrade process may take a few minutes to complete. During this time, your Tobiko Cloud project will be unavailable.
+
+    Any in-progress plans and runs will be aborted:
+
+      - Aborted plans will be stopped, and you must **manually** start them again.
+      - Aborted runs will be automatically resumed shortly after the upgrade completes.
+
+    To avoid unexpected interruptions, please notify your team before starting the upgrade.
+
+### Latest Version
+
+Click the **Upgrade Now** button and confirm to begin upgrading your project to the latest version.
+
+![Tobiko Cloud Upgrade Page](./upgrade/upgrade-ui-latest.png)
+
+### Custom Version
+
+We recommend upgrading your Tobiko Cloud project to the latest version, but you may prefer to upgrade to a specific version.
+
+For example, consider a team that has separate staging and production Tobiko Cloud projects. They upgrade the staging project first, run tests, and only upgrade the production project after verifying that staging works as expected.
+
+If a new version of Tobiko Cloud is released during this testing period, the latest available version will not match the version tested in staging. The team can specify a custom Tobiko Cloud version to upgrade production to the specific version that was already tested in staging.
+
+To specify a custom version, select the **Custom** tab on the Upgrade page and enter your desired version in the text box.
+
+![Tobiko Cloud Upgrade Custom Version](./upgrade/upgrade-ui-custom-version.png)
+
+Make sure you are entering a valid custom version by:
+
+  - Entering the custom version **without** the leading `v`
+  - Confirming that the version is valid and later than the current version of the project
+
+If your custom version is not valid, Tobiko Cloud will display an error message.
+
+After entering the custom version, click the **Upgrade Now** button and confirm to begin the upgrade process.
+
+## Upgrade Progress
+
+Tobiko Cloud will display a progress page while the upgrade is in progress:
+
+![Tobiko Cloud Upgrade Progress](./upgrade/upgrade-ui-progress.png)
+
+Once the upgrade is complete, Tobiko Cloud will automatically redirect you back to your upgraded project.
+
+## Upgrade Support
+
+If you encounter an issue during the upgrade process, please [report an incident](./incident_reporting.md). Our support team will follow up as soon as possible.
+
+For the quickest response, we recommend upgrading Monday through Friday between 9am and 5pm PST.

docs/cloud/features/upgrade/upgrade-ui-custom-version.png

@@ -102,6 +102,8 @@ For example, pre/post-statements might modify settings or create indexes. Howeve
 
 You can set the `pre_statements` and `post_statements` arguments to a list of SQL strings, SQLGlot expressions, or macro calls to define the model's pre/post-statements.
 
+**Project-level defaults:** You can also define pre/post-statements at the project level using `model_defaults` in your configuration. These will be applied to all models in your project and merged with any model-specific statements. Default statements are executed first, followed by model-specific statements. Learn more about this in the [model configuration reference](../../reference/model_configuration.md#model-defaults).
+
 ``` python linenums="1" hl_lines="8-12"
 @model(
     "db.test_model",
@@ -182,6 +184,8 @@ These can be used, for example, to grant privileges on views of the virtual laye
 
 Similar to pre/post-statements you can set the `on_virtual_update` argument in the `@model` decorator to a list of SQL strings, SQLGlot expressions, or macro calls.
 
+**Project-level defaults:** You can also define on-virtual-update statements at the project level using `model_defaults` in your configuration. These will be applied to all models in your project (including Python models) and merged with any model-specific statements. Default statements are executed first, followed by model-specific statements. Learn more about this in the [model configuration reference](../../reference/model_configuration.md#model-defaults).
+
 ``` python linenums="1" hl_lines="8"
 @model(
     "db.test_model",
@@ -394,6 +398,35 @@ It's also possible to use the `@EACH` macro, combined with a global list variabl
 ...
 ```
 
+## Using macros in model properties
+
+Python models support macro variables in model properties. However, special care must be taken when the macro variable appears within a string.
+
+For example when using macro variables inside cron expressions, you need to wrap the entire expression in quotes and prefix it with `@` to ensure proper parsing:
+
+```python linenums="1"
+# Correct: Wrap the cron expression containing a macro variable
+@model(
+    "my_model",
+    cron="@'*/@{mins} * * * *'",  # Note the @'...' syntax
+    ...
+)
+
+# This also works with blueprint variables
+@model(
+    "@{customer}.scheduled_model",
+    cron="@'0 @{hour} * * *'",
+    blueprints=[
+        {"customer": "customer_1", "hour": 2}, # Runs at 2 AM
+        {"customer": "customer_2", "hour": 8}, # Runs at 8 AM
+    ],
+    ...
+)
+
+```
+
+This is necessary because cron expressions often use `@` for aliases (like `@daily`, `@hourly`), which can conflict with SQLMesh's macro syntax.
+
 ## Examples
 ### Basic
 The following is an example of a Python model returning a static Pandas DataFrame.

docs/cloud/features/upgrade/upgrade-ui-latest.png

@@ -203,6 +203,8 @@ ALTER SESSION SET TIMEZONE = 'PST';
 
 Seed models also support on-virtual-update statements, which are executed after the completion of the [Virtual Update](#virtual-update).
 
+**Project-level defaults:** You can also define on-virtual-update statements at the project level using `model_defaults` in your configuration. These will be applied to all models in your project (including seed models) and merged with any model-specific statements. Default statements are executed first, followed by model-specific statements. Learn more about this in the [model configuration reference](../../reference/model_configuration.md#model-defaults).
+
 These must be enclosed within an `ON_VIRTUAL_UPDATE_BEGIN;` ...; `ON_VIRTUAL_UPDATE_END;` block:
 
 ```sql linenums="1" hl_lines="8-13"