[auto] adding content to emb-691-adjust-rspack-configs->master (#392)

Co-authored-by: Metabase Docs bot <[email protected]>

Author: github-automation-metabase

_docs/master/developers-guide/devenv.md

@@ -88,7 +88,7 @@ There is also an option to reload changes on save without hot reloading if you p
 $ yarn build-watch
 ```
 
-Some systems may have trouble detecting changes to frontend files. You can enable filesystem polling by uncommenting the `watchOptions` clause in `webpack.config.js`. If you do this it may be worth making git ignore changes to webpack config, using `git update-index --assume-unchanged webpack.config.js`
+Some systems may have trouble detecting changes to frontend files. You can enable filesystem polling by uncommenting the `watchOptions` clause in `rspack.main.config.js`. If you do this it may be worth making git ignore changes to webpack config, using `git update-index --assume-unchanged rspack.main.config.js`
 
 We exclude ESLint loader in dev mode for seven times quicker initial builds by default. You can enable it by exporting an environment variable:
 

_docs/master/embedding/sdk/upgrade.md

@@ -0,0 +1,83 @@
+---
+version: master
+has_magic_breadcrumbs: true
+show_category_breadcrumb: true
+show_title_breadcrumb: true
+category: Embedding
+title: 'Upgrading Metabase and the Embedded analytics SDK'
+source_url: 'https://github.com/metabase/metabase/blob/master/docs/embedding/sdk/upgrade.md'
+layout: new-docs
+summary: 'How to upgrade your Metabase and Embedded analytics SDK versions, test the changes, and check for breaking changes that might affect your app.'
+---
+
+# Upgrading Metabase and the Embedded analytics SDK
+
+Here's a basic overview of the steps you'll want to take when upgrading your SDK.
+
+## 1. Read the release post and changelog for both Metabase and the Embedded analytics SDK
+
+- [Release posts](/releases) give a good overview of what's in each release, and call out breaking changes (which are rare).
+- [Metabase changelogs](/changelog) list Metabase changes.
+- [Embedded analytics SDK changelogs](/changelog/55) list changes specific to the SDK package.
+
+Check for any relevant changes, especially breaking changes that require you to update your application's code. If there are breaking changes, we'll have docs that'll walk you through what changes you'll need to make and why.
+
+## 2. Test the upgrade
+
+When upgrading to a new major version, you'll want to upgrade both Metabase and the SDK version in parallel, as having Metabase and the SDK major versions out of sync can cause errors.
+
+### Spin up the new version of Metabase for testing
+
+You can do this locally or in a dev instance. If your testing setup involves a lot of test user accounts, getting a [development instance](../../installation-and-operation/development-instance) could be more cost-effective.
+
+See [upgrading Metabase](../../installation-and-operation/upgrading-metabase).
+
+### Upgrade the SDK with npm or yarn
+
+You'll want to test the changes locally first, as there may be breaking changes that require you to upgrade your application code.
+
+Check out a new branch in your application and install the next stable version, either with npm or yarn:
+
+Via npm:
+
+```bash
+npm install @metabase/embedding-sdk-react@{next-major-version-number}-stable
+```
+
+For example, if you were upgrading to version 55 of the SDK:
+
+```bash
+npm install @metabase/embedding-sdk-react@55-stable
+```
+
+If you're using yarn:
+
+```bash
+yarn add @metabase/embedding-sdk-react@{next-major-version-number}-stable
+```
+
+See more on [SDK versions](./version).
+
+### If there are breaking changes, make the necessary changes to your application code
+
+Breaking changes are rare, but if you do need to make changes, we'll mention it in the release notes for the new major version and have docs that walk you through the changes.
+
+Update or add tests for any application code changes that you make.
+
+### Deploy to your staging environment
+
+Before deploying your app to your staging environment, make sure you've tested your app locally (manually, as well as running any automated tests).
+
+If all goes well with your local tests, deploy to your staging environment. Check that the Metabase embeds in your staging app are still working as expected, and perform any other testing you normally do with your application with respect to your embedded analytics.
+
+## 3. Deploy to production
+
+If everything is working in staging, you're ready to deploy to production.
+
+Be sure to deploy your application changes and upgrade your Metabase in parallel so that the SDK version and the Metabase version stay in sync.
+
+### If your instance is on Metabase Cloud, you'll need to request an upgrade
+
+If you're on Metabase Cloud, your instance version is pinned, so you'll need to request an upgrade by [contacting support](/help-premium).
+
+We'll coordinate with you so that your instance is upgraded when you deploy the changes to your application.

_docs/master/permissions/images/advanced-example-1-sandbox-modal.png

@@ -64,6 +64,7 @@ For an introduction to expressions, check out the [overview of custom expression
     - [concat](./expressions/concat)
     - [contains](#contains)
     - [date](#date)
+    - [datetime](#datetime)
     - [doesNotContain](#doesnotcontain)
     - [domain](#domain)
     - [endsWith](#endswith)
@@ -107,6 +108,8 @@ For an introduction to expressions, check out the [overview of custom expression
     - [quarterName](#quartername)
     - [relativeDateTime](#relativedatetime)
     - [second](#second)
+    - [timeSpan](#timespan)
+    - [today](#today)
     - [week](#week)
     - [weekday](#weekday)
     - [year](#year)
@@ -434,7 +437,7 @@ Example: `sqrt([Hypotenuse])`.
 
 Databases that don't support `sqrt`: SQLite.
 
-Related: [Power](#power).
+Related: [power](#power).
 
 ## String functions
 
@@ -501,9 +504,12 @@ Related: [datetime](#datetime)
 
 > Available on PostgreSQL, MySQL/MariaDB, BigQuery, Redshift, ClickHouse, and Snowflake
 
-Converts a datetime string to a datetime.
+Converts a datetime string or bytes to a datetime.
 
-Syntax: `datetime(column)`
+Syntax: `datetime(value, mode)`
+
+- `value`: The string, bytes, or number to convert to a datetime.
+- `mode`: Optional. The mode indicating the format. One of: `"simple"`, `"iso"`, `"simpleBytes"`, `"isoBytes"`, `"unixSeconds"`, `"unixMilliseconds"`, `"unixMicroseconds"`, `"unixNanoseconds"`. Default is `"iso"`.
 
 Example: `datetime("2025-03-20 12:45:04")`
 
@@ -938,6 +944,16 @@ Syntax: `timeSpan(number, text)`
 
 Example: `[Orders → Created At] + timeSpan(7, "day")` will return the date 7 days after the `Created At` date.
 
+### today
+
+Returns the current date (without time).
+
+Syntax: `today()`
+
+Example: `today()` would return the current date, such as `2025-05-04`.
+
+Related: [now](#now).
+
 ### [week](./expressions/week)
 
 Takes a datetime and returns the week as an integer.

_docs/master/questions/query-builder/expressions-list.md

@@ -4917,7 +4917,7 @@ <h2 id="frontend-development">Frontend development</h2>
 <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span>yarn build-watch
 </code></pre></div></div>
 
-<p>Some systems may have trouble detecting changes to frontend files. You can enable filesystem polling by uncommenting the <code class="language-plaintext highlighter-rouge">watchOptions</code> clause in <code class="language-plaintext highlighter-rouge">webpack.config.js</code>. If you do this it may be worth making git ignore changes to webpack config, using <code class="language-plaintext highlighter-rouge">git update-index --assume-unchanged webpack.config.js</code></p>
+<p>Some systems may have trouble detecting changes to frontend files. You can enable filesystem polling by uncommenting the <code class="language-plaintext highlighter-rouge">watchOptions</code> clause in <code class="language-plaintext highlighter-rouge">rspack.main.config.js</code>. If you do this it may be worth making git ignore changes to webpack config, using <code class="language-plaintext highlighter-rouge">git update-index --assume-unchanged rspack.main.config.js</code></p>
 
 <p>We exclude ESLint loader in dev mode for seven times quicker initial builds by default. You can enable it by exporting an environment variable:</p>