Merge branch 'main' into fix/redshift-iam-db-user

Author: synthpieter

.github/workflows/pr.yaml

@@ -188,15 +188,15 @@ jobs:
 
   ui-style:
     needs: [changes]
-    if:
-      needs.changes.outputs.client == 'true' || needs.changes.outputs.ci ==
-      'true' || github.ref == 'refs/heads/main'
+    if: false
+      # needs.changes.outputs.client == 'true' || needs.changes.outputs.ci ==
+      # 'true' || github.ref == 'refs/heads/main'
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
       - uses: actions/setup-node@v6
         with:
-          node-version: '20'
+          node-version: '22'
       - uses: pnpm/action-setup@v4
         with:
           version: latest
@@ -396,6 +396,7 @@ jobs:
     env:
       PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD: 1
     runs-on: ubuntu-latest
+    if: false
     steps:
       - uses: actions/checkout@v5
       - uses: actions/setup-node@v6

.github/workflows/release.yaml

@@ -12,12 +12,12 @@ jobs:
       - uses: actions/checkout@v5
       - uses: actions/setup-node@v6
         with:
-          node-version: '20'
+          node-version: '22'
       - uses: pnpm/action-setup@v4
         with:
           version: latest
       - name: Install dependencies
-        run: pnpm install
+        run: pnpm install --frozen-lockfile
       - name: Build UI
         run: pnpm --prefix web/client run build
       - name: Upload UI build artifact

.github/workflows/release_extension.yaml

@@ -30,7 +30,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: '20'
+          node-version: '22'
       - name: Install pnpm
         uses: pnpm/action-setup@v4
         with:

.github/workflows/release_shared_js.yaml

@@ -33,7 +33,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: '20'
+          node-version: '22'
           registry-url: 'https://registry.npmjs.org'
       - name: Update npm
         run: npm install -g npm@latest

.nvmrc

@@ -1 +1 @@
-20
+22

docs/cloud/features/scheduler/airflow.md

@@ -35,7 +35,7 @@ Start by installing the `tobiko-cloud-scheduler-facade` library in your Airflow
 Make sure to include the `[airflow]` extra in the installation command:
 
 ``` bash
-$ pip install tobiko-cloud-scheduler-facade[airflow]
+pip install tobiko-cloud-scheduler-facade[airflow]
 ```
 
 !!! info "Mac Users"

docs/cloud/features/scheduler/dagster.md

@@ -48,7 +48,7 @@ dependencies = [
 And then install it into the Python environment used by your Dagster project:
 
 ```sh
-$ pip install -e '.[dev]'
+pip install -e '.[dev]'
 ```
 
 ### Connect Dagster to Tobiko Cloud

docs/cloud/features/security/single_sign_on.md

@@ -145,7 +145,7 @@ Here is what you will see if you are accessing Tobiko Cloud via Okta. Click on t
 You can see what the status of your session is with the `status` command:
 
 ``` bash
-$ tcloud auth status
+tcloud auth status
 ```
 
 
@@ -156,7 +156,7 @@ $ tcloud auth status
 Run the `login` command to begin the login process:
 
 ``` bash
-$ tcloud auth login
+tcloud auth login
 ```
 
 ![tcloud_login](./single_sign_on/tcloud_login.png)
@@ -183,11 +183,11 @@ Current Tobiko Cloud SSO session expires in 1439 minutes
 In order to delete your session information you can use the log out command:
 
 ``` bash
-> tcloud auth logout
-Logged out of Tobiko Cloud
+tcloud auth logout
+# Logged out of Tobiko Cloud
 
-> tcloud auth status
-Not currently authenticated
+tcloud auth status
+# Not currently authenticated
 ```
 
 ![tcloud_logout](./single_sign_on/tcloud_logout.png)

docs/cloud/features/xdb_diffing.md

@@ -47,7 +47,7 @@ Then, specify each table's gateway in the `table_diff` command with this syntax:
 For example, we could diff the `landing.table` table across `bigquery` and `snowflake` gateways like this:
 
 ```sh
-$ tcloud sqlmesh table_diff 'bigquery|landing.table:snowflake|landing.table'
+tcloud sqlmesh table_diff 'bigquery|landing.table:snowflake|landing.table'
 ```
 
 This syntax tells SQLMesh to use the cross-database diffing algorithm instead of the normal within-database diffing algorithm.

docs/concepts/state.md

@@ -92,7 +92,7 @@ The state file is a simple `json` file that looks like:
 You can export a specific environment like so:
 
 ```sh
-$ sqlmesh state export --environment my_dev -o my_dev_state.json
+sqlmesh state export --environment my_dev -o my_dev_state.json
 ```
 
 Note that every snapshot that is part of the environment will be exported, not just the differences from `prod`. The reason for this is so that the environment can be fully imported elsewhere without any assumptions about which snapshots are already present in state.
@@ -102,7 +102,7 @@ Note that every snapshot that is part of the environment will be exported, not j
 You can export local state like so:
 
 ```bash
-$ sqlmesh state export --local -o local_state.json
+sqlmesh state export --local -o local_state.json
 ```
 
 This essentially just exports the state of the local context which includes local changes that have not been applied to any virtual data environments.
@@ -174,10 +174,11 @@ If your project has [multiple gateways](../guides/configuration.md#gateways) wit
 
 ```bash
 # state export
-$ sqlmesh --gateway <gateway> state export -o state.json
-
+sqlmesh --gateway <gateway> state export -o state.json
+```
+```bash
 # state import
-$ sqlmesh --gateway <gateway> state import -i state.json
+sqlmesh --gateway <gateway> state import -i state.json
 ```
 
 ## Version Compatibility