[auto] adding content to docs/latest-docker-version->master (#358)

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

Author: github-automation-metabase

_docs/master/developers-guide/community-drivers.md

@@ -45,6 +45,7 @@ Anyone can build a community driver. These are the currently known third-party d
 | [GreptimeDB](https://github.com/greptimeteam/greptimedb-metabase-driver)              | ![GitHub stars](https://img.shields.io/github/stars/greptimeteam/greptimedb-metabase-driver)       | ![GitHub (Pre-)Release Date](https://img.shields.io/github/release-date-pre/greptimeteam/greptimedb-metabase-driver)       |
 | [Hydra](https://www.hydra.so/blog-posts/2022-09-28-metabase-and-hydra)                | Hydra connections use the official [Postgres driver](../databases/connections/postgresql).      | Not applicable.                                                                                                            |
 | [Impala](https://github.com/brenoae/metabase-impala-driver)                           | ![GitHub stars](https://img.shields.io/github/stars/brenoae/metabase-impala-driver)                | ![GitHub (Pre-)Release Date](https://img.shields.io/github/release-date-pre/brenoae/metabase-impala-driver)                |
+| [InterSystems IRIS](https://github.com/Siddardar/metabase-iris-driver/tree/main)      | ![GitHub stars](https://img.shields.io/github/stars/Siddardar/metabase-iris-driver)                | ![GitHub (Pre-)Release Date](https://img.shields.io/github/release-date-pre/Siddardar/metabase-iris-driver)                |
 | [Materialize](https://github.com/MaterializeInc/metabase-materialize-driver)          | ![GitHub stars](https://img.shields.io/github/stars/MaterializeInc/metabase-materialize-driver)    | ![GitHub (Pre-)Release Date](https://img.shields.io/github/release-date-pre/MaterializeInc/metabase-materialize-driver)    |
 | [Neo4j](https://github.com/StronkMan/metabase-neo4j-driver)                           | ![GitHub stars](https://img.shields.io/github/stars/StronkMan/metabase-neo4j-driver)               | ![GitHub (Pre-)Release Date](https://img.shields.io/github/release-date-pre/StronkMan/metabase-neo4j-driver)               |
 | [Netsuite SuiteAnalytics Connect](https://github.com/ericcj/metabase-netsuite-driver) | ![GitHub stars](https://img.shields.io/github/stars/ericcj/metabase-netsuite-driver)               | ![GitHub (Pre-)Release Date](https://img.shields.io/github/release-date-pre/ericcj/metabase-netsuite-driver)               |

_docs/master/installation-and-operation/activating-the-enterprise-edition.md

@@ -56,7 +56,7 @@ To get all the features available when upgrading to a _self-hosted_ [Pro or Ente
 Assuming you've been using a [production application database](../installation-and-operation/configuring-application-database), you'll want to:
 
 1. [Back up your application database](./backing-up-metabase-application-data).
-2. Download the Enterprise Edition version that corresponds with your current Metabase version. So if you're running the Docker image for {{site.data.latest_version}}, you should switch to the Docker image for {{site.data.latest_enterprise}}. To see a list of available versions for both the Open Source and Enterprise Editions, check out [Metabase releases](https://github.com/metabase/metabase/releases).
+2. Download the Enterprise Edition version that corresponds with your current Metabase version. So if you're running the Docker image for {{site.latest_version}}, you should switch to the Docker image for {{site.latest_enterprise}}. To see a list of available versions for both the Open Source and Enterprise Editions, check out [Metabase releases](https://github.com/metabase/metabase/releases).
 3. Stop your current Metabase Open Source edition.
 4. Swap in the Enterprise Edition Docker image or jar that you downloaded.
 5. Start your Metabase like you normally would using the new Enterprise Edition image or jar. You don't need to do anything with your application database (which you've backed up in step one, right?).

_docs/master/installation-and-operation/upgrading-metabase.md

@@ -147,6 +147,8 @@ Durning a **minor version upgrade** (e.g., 54.1 to 54.2), the new Metabase conta
 
 ## Rolling back an upgrade or to an older version
 
+> **The downgrade command must be run on the JAR with the higher version number.**
+
 In general, regular backups (especially backups before upgrading), are the best policy, so we recommend reverting to a backup of your application database to roll back an upgrade.
 
 But if you've made any change (adding new questions/dashboards, etc) since upgrading that you want to keep, you may be able to use the `migrate down` command to roll back your Metabase application database to support the previous Metabase version you were running. When Metabase upgrades to a new version, it runs migrations that may change the application database schema. The `migrate down` command undoes those schema changes. In general, we recommend restoring from a backup (the backup that you definitely remembered to generate before upgrading), and only using the `migrate down` command if you really need to keep changes made after your upgrade.

_site/docs/master/developers-guide/community-drivers.html

@@ -4810,6 +4810,11 @@ <h2 id="community-drivers-1">Community drivers</h2>
       <td data-label="GitHub Stars"><img src="https://img.shields.io/github/stars/brenoae/metabase-impala-driver" alt="GitHub stars"></td>
       <td data-label="Last release (if available)"><img src="https://img.shields.io/github/release-date-pre/brenoae/metabase-impala-driver" alt="GitHub (Pre-)Release Date"></td>
     </tr>
+    <tr>
+      <td data-label="Database"><a href="https://github.com/Siddardar/metabase-iris-driver/tree/main">InterSystems IRIS</a></td>
+      <td data-label="GitHub Stars"><img src="https://img.shields.io/github/stars/Siddardar/metabase-iris-driver" alt="GitHub stars"></td>
+      <td data-label="Last release (if available)"><img src="https://img.shields.io/github/release-date-pre/Siddardar/metabase-iris-driver" alt="GitHub (Pre-)Release Date"></td>
+    </tr>
     <tr>
       <td data-label="Database"><a href="https://github.com/MaterializeInc/metabase-materialize-driver">Materialize</a></td>
       <td data-label="GitHub Stars"><img src="https://img.shields.io/github/stars/MaterializeInc/metabase-materialize-driver" alt="GitHub stars"></td>

_site/docs/master/installation-and-operation/activating-the-enterprise-edition.html

@@ -4779,7 +4779,7 @@ <h2 id="upgrading-from-a-self-hosted-metabase-open-source-edition-to-a-pro-or-en
 
 <ol>
   <li><a href="./backing-up-metabase-application-data">Back up your application database</a>.</li>
-  <li>Download the Enterprise Edition version that corresponds with your current Metabase version. So if you’re running the Docker image for , you should switch to the Docker image for . To see a list of available versions for both the Open Source and Enterprise Editions, check out <a href="https://github.com/metabase/metabase/releases">Metabase releases</a>.</li>
+  <li>Download the Enterprise Edition version that corresponds with your current Metabase version. So if you’re running the Docker image for v0.55.2, you should switch to the Docker image for v1.55.2. To see a list of available versions for both the Open Source and Enterprise Editions, check out <a href="https://github.com/metabase/metabase/releases">Metabase releases</a>.</li>
   <li>Stop your current Metabase Open Source edition.</li>
   <li>Swap in the Enterprise Edition Docker image or jar that you downloaded.</li>
   <li>Start your Metabase like you normally would using the new Enterprise Edition image or jar. You don’t need to do anything with your application database (which you’ve backed up in step one, right?).</li>

_site/docs/master/installation-and-operation/upgrading-metabase.html

@@ -4881,6 +4881,10 @@ <h2 id="what-happens-during-an-upgrade-or-downgrade">What happens during an upgr
 
 <h2 id="rolling-back-an-upgrade-or-to-an-older-version">Rolling back an upgrade or to an older version</h2>
 
+<blockquote>
+  <p><strong>The downgrade command must be run on the JAR with the higher version number.</strong></p>
+</blockquote>
+
 <p>In general, regular backups (especially backups before upgrading), are the best policy, so we recommend reverting to a backup of your application database to roll back an upgrade.</p>
 
 <p>But if you’ve made any change (adding new questions/dashboards, etc) since upgrading that you want to keep, you may be able to use the <code class="language-plaintext highlighter-rouge">migrate down</code> command to roll back your Metabase application database to support the previous Metabase version you were running. When Metabase upgrades to a new version, it runs migrations that may change the application database schema. The <code class="language-plaintext highlighter-rouge">migrate down</code> command undoes those schema changes. In general, we recommend restoring from a backup (the backup that you definitely remembered to generate before upgrading), and only using the <code class="language-plaintext highlighter-rouge">migrate down</code> command if you really need to keep changes made after your upgrade.</p>