Archive cross-version documentation for v22.2 and earlier

Complete 3-step cross-version archival process removing support for
v22.2, v22.1, v21.2, v21.1, v20.2, and v2.1 documentation versions.

**Major Changes:**
- Delete 1,769 archived version image assets
- Fix 40+ cross-version references to point to supported versions
- Update backward-incompatible links to use v23.2 (earliest supported)
- Fix Jekyll SSL certificate verification for Ruby 3.4.3 + macOS
- Add required Ruby 3.x gem dependencies

**Cross-Version Link Fixes:**
- Fix backward-incompatible files (9 files): v22.2 Jekyll links → v23.2 relative paths
- Fix show-ranges deprecation notices: v22.2 links → archived documentation
- Fix release notes and Kubernetes upgrade references
- Fix replication zone mapping references across all supported versions

**Infrastructure:**
- Preserve existing minimal infrastructure (releases/v*.md stub pages)
- Add openssl_fix.rb for Jekyll SSL bypass
- Update Gemfile with Ruby 3.x compatibility gems
- Fix Liquid syntax errors in image paths

**Verification:**
- All corrected links verified to exist and function
- Cross-version references now cleanly separated (v23.1+ supported)
- Jekyll server compatibility restored

Author: ebembi-crdb

src/current/Gemfile

@@ -13,6 +13,11 @@ gem "redcarpet", "~> 3.6"
 gem "rss"
 gem "webrick"
 gem "jekyll-minifier"
+gem 'csv'
+gem 'logger'
+gem 'base64'
+gem 'bigdecimal'
+gem 'mutex_m'
 
 group :jekyll_plugins do
     gem "jekyll-include-cache"

src/current/_includes/releases/v23.1/v23.1.3.md

@@ -3,7 +3,7 @@
 Release Date: June 13, 2023
 
 {{site.data.alerts.callout_danger}}
-A [bug](https://github.com/cockroachdb/cockroach/issues/104798) was discovered in a change included in v23.1.3 (this release). This bug can affect clusters upgrading to v23.1.3 from [v22.2.x]({% link releases/v22.2.md %}). In an affected cluster, jobs that were running during the upgrade could hang or fail to run after the upgrade is finalized. Users upgrading from v22.2.x are advised to use [v23.1.2](#v23-1-2) to upgrade, or to set the [`cluster.preserve_downgrade_option`]({% link v23.1/upgrade-cockroach-version.md %}#step-3-decide-how-the-upgrade-will-be-finalized) cluster setting to delay finalization of the upgrade until they can upgrade to v23.1.4.
+A [bug](https://github.com/cockroachdb/cockroach/issues/104798) was discovered in a change included in v23.1.3 (this release). This bug can affect clusters upgrading to v23.1.3 from [v22.2.x]({% link releases/v22.2.md %}). In an affected cluster, jobs that were running during the upgrade could hang or fail to run after the upgrade is finalized. Users upgrading from v22.2.x are advised to use [v23.1.2](#v23-1-2) to upgrade, or to set the `cluster.preserve_downgrade_option` cluster setting to delay finalization of the upgrade until they can upgrade to v23.1.4.
 {{site.data.alerts.end}}
 
 {% include releases/new-release-downloads-docker-image.md release=include.release %}

src/current/_includes/v23.1/backward-incompatible/alpha.1.md

@@ -7,9 +7,9 @@
     - Optional: keep port `26257` for RPC, and allocate a new port, e.g., `26357`, for SQL connections. For example, you might configure a node with the flags `--listen-addr=:26257 --sql-addr=:26357`. When using this mode of operation, the `--join` flags do not need to be modified. However, SQL client apps or the SQL load balancer configuration (when in use) must be updated to use the new SQL port number. [#85671][#85671]
 - If no `nullif` option is specified while using [`IMPORT CSV`](../v23.1/import.html), then a zero-length string in the input is now treated as `NULL`. The quoted empty string in the input is treated as an empty string. Similarly, if `nullif` is specified, then an unquoted value is treated as `NULL`, and a quoted value is treated as that string. These changes were made to make `IMPORT CSV` behave more similarly to `COPY CSV`. If the previous behavior (i.e., treating either quoted or unquoted values that match the `nullif` setting as `NULL`) is desired, you can use the new `allow_quoted_null` option in the `IMPORT` statement. [#84487][#84487]
 - [`COPY FROM`](../v23.1/copy.html) operations are now atomic by default instead of being segmented into 100 row transactions. Set the `copy_from_atomic_enabled` session setting to `false` for the previous behavior. [#85986][#85986]
-- The `GRANT` privilege has been removed and replaced by the more granular [`WITH GRANT OPTION`]({% link v22.2/grant.md %}#grant-privileges-with-the-option-to-grant-to-others), which provides control over which privileges are allowed to be granted. [#81310][#81310]
+- The `GRANT` privilege has been removed and replaced by the more granular [`WITH GRANT OPTION`](../v23.2/grant.html#grant-privileges-with-the-option-to-grant-to-others), which provides control over which privileges are allowed to be granted. [#81310][#81310]
 - Removed the ability to cast `int`, `int2`, and `int8` to a `0` length `BIT` or `VARBIT`. [#81266][#81266]
 - Removed the deprecated `GRANT` privilege. [#81310][#81310]
 - Removed the `ttl_automatic_column` storage parameter. The `crdb_internal_expiration` column is created when `ttl_expire_after` is set and removed when `ttl_expire_after` is reset. [#83134][#83134]
 - Removed the byte string parameter in the `crdb_internal.schedule_sql_stats_compaction` function. [#82560][#82560]
-- Changed the default value of the `enable_implicit_transaction_for_batch_statements` to `true`. This means that a [batch of statements]({% link v22.2/transactions.md %}#batched-statements) sent in one string separated by semicolons is treated as an implicit transaction. [#76834][#76834]
+- Changed the default value of the `enable_implicit_transaction_for_batch_statements` to `true`. This means that a [batch of statements](../v23.2/transactions.html#batched-statements) sent in one string separated by semicolons is treated as an implicit transaction. [#76834][#76834]

src/current/_includes/v23.1/orchestration/kubernetes-upgrade-cluster-helm.md

@@ -6,7 +6,7 @@
 
     Therefore, in order to upgrade to {{ page.version.version }}, you must be on a production release of {{ previous_version }}.
 
-    1. If you are upgrading to {{ page.version.version }} from a production release earlier than {{ previous_version }}, or from a testing release (alpha/beta), first [upgrade to a production release of {{ previous_version }}]({% link {{ previous_version }}/upgrade-cockroachdb-kubernetes.md %}?filters=helm). Be sure to complete all the steps.
+    1. If you are upgrading to {{ page.version.version }} from a production release earlier than {{ previous_version }}, or from a testing release (alpha/beta), first upgrade to a production release of {{ previous_version }}. See the [archived version documentation]({% link releases/unsupported-versions.md %}) for upgrade instructions. Be sure to complete all the steps.
 
     1. Then return to this page and perform a second upgrade to {{ page.version.version }}.
 

src/current/_includes/v23.1/orchestration/kubernetes-upgrade-cluster-manual.md

@@ -6,7 +6,7 @@
 
     Therefore, in order to upgrade to {{ page.version.version }}, you must be on a production release of {{ previous_version }}.
 
-    1. If you are upgrading to {{ page.version.version }} from a production release earlier than {{ previous_version }}, or from a testing release (alpha/beta), first [upgrade to a production release of {{ previous_version }}]({% link {{ previous_version }}/upgrade-cockroachdb-kubernetes.md %}?filters=manual). Be sure to complete all the steps.
+    1. If you are upgrading to {{ page.version.version }} from a production release earlier than {{ previous_version }}, or from a testing release (alpha/beta), first upgrade to a production release of {{ previous_version }}. See the [archived version documentation]({% link releases/unsupported-versions.md %}) for upgrade instructions. Be sure to complete all the steps.
 
     1. Then return to this page and perform a second upgrade to {{ page.version.version }}.
 

src/current/_includes/v23.1/sql/replication-zone-patterns-to-multiregion-sql-mapping.md

@@ -1,5 +1,5 @@
 | Replication Zone Pattern                         | Multi-Region SQL                                                                                                                                    |
 |--------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [Duplicate indexes]({% link v20.2/topology-duplicate-indexes.md %})                  | [`GLOBAL` tables]({% link {{ page.version.version }}/global-tables.md %})                                                                                                                       |
-| [Geo-partitioned replicas]({% link v20.2/topology-geo-partitioned-replicas.md %})        | [`REGIONAL BY ROW` tables]({% link {{ page.version.version }}/regional-tables.md %}#regional-by-row-tables) with [`ZONE` survival goals](multiregion-survival-goals.html#survive-zone-failures)     |
-| [Geo-partitioned leaseholders]({% link v20.2/topology-geo-partitioned-leaseholders.md %}) | [`REGIONAL BY ROW` tables]({% link {{ page.version.version }}/regional-tables.md %}#regional-by-row-tables) with [`REGION` survival goals](multiregion-survival-goals.html#survive-region-failures) |
+| Duplicate indexes (deprecated pattern)                  | [`GLOBAL` tables]({% link {{ page.version.version }}/global-tables.md %})                                                                                                                       |
+| Geo-partitioned replicas (deprecated pattern)        | [`REGIONAL BY ROW` tables]({% link {{ page.version.version }}/regional-tables.md %}#regional-by-row-tables) with [`ZONE` survival goals](multiregion-survival-goals.html#survive-zone-failures)     |
+| Geo-partitioned leaseholders (deprecated pattern) | [`REGIONAL BY ROW` tables]({% link {{ page.version.version }}/regional-tables.md %}#regional-by-row-tables) with [`REGION` survival goals](multiregion-survival-goals.html#survive-region-failures) |

src/current/_includes/v23.1/sql/show-ranges-output-deprecation-notice.md

@@ -5,7 +5,7 @@ The statement syntax and output documented on this page use the updated `SHOW RA
 SET CLUSTER SETTING sql.show_ranges_deprecated_behavior.enabled = false;
 ~~~
 
-The pre-v23.1 output of `SHOW RANGES` is deprecated in v23.1 **and will be removed in v23.2**. To view the documentation for the deprecated version of the `SHOW RANGES` statement, see [`SHOW RANGES` (v22.2)]({% link v22.2/show-ranges.md %}).
+The pre-v23.1 output of `SHOW RANGES` is deprecated in v23.1 **and will be removed in v23.2**. To view the documentation for the deprecated version of the `SHOW RANGES` statement, see the [archived version documentation]({% link releases/unsupported-versions.md %}).
 
 When you use the deprecated version of the `SHOW RANGES` statement, the following message will appear, reminding you to update [the cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}#setting-sql-show-ranges-deprecated-behavior-enabled):
 

src/current/_includes/v23.2/backward-incompatible/alpha.1.md

@@ -7,9 +7,9 @@
     - Optional: keep port `26257` for RPC, and allocate a new port, e.g., `26357`, for SQL connections. For example, you might configure a node with the flags `--listen-addr=:26257 --sql-addr=:26357`. When using this mode of operation, the `--join` flags do not need to be modified. However, SQL client apps or the SQL load balancer configuration (when in use) must be updated to use the new SQL port number. [#85671][#85671]
 - If no `nullif` option is specified while using [`IMPORT CSV`](../v23.1/import.html), then a zero-length string in the input is now treated as `NULL`. The quoted empty string in the input is treated as an empty string. Similarly, if `nullif` is specified, then an unquoted value is treated as `NULL`, and a quoted value is treated as that string. These changes were made to make `IMPORT CSV` behave more similarly to `COPY CSV`. If the previous behavior (i.e., treating either quoted or unquoted values that match the `nullif` setting as `NULL`) is desired, you can use the new `allow_quoted_null` option in the `IMPORT` statement. [#84487][#84487]
 - [`COPY FROM`](../v23.1/copy.html) operations are now atomic by default instead of being segmented into 100 row transactions. Set the `copy_from_atomic_enabled` session setting to `false` for the previous behavior. [#85986][#85986]
-- The `GRANT` privilege has been removed and replaced by the more granular [`WITH GRANT OPTION`]({% link v22.2/grant.md %}#grant-privileges-with-the-option-to-grant-to-others), which provides control over which privileges are allowed to be granted. [#81310][#81310]
+- The `GRANT` privilege has been removed and replaced by the more granular [`WITH GRANT OPTION`](../v23.2/grant.html#grant-privileges-with-the-option-to-grant-to-others), which provides control over which privileges are allowed to be granted. [#81310][#81310]
 - Removed the ability to cast `int`, `int2`, and `int8` to a `0` length `BIT` or `VARBIT`. [#81266][#81266]
 - Removed the deprecated `GRANT` privilege. [#81310][#81310]
 - Removed the `ttl_automatic_column` storage parameter. The `crdb_internal_expiration` column is created when `ttl_expire_after` is set and removed when `ttl_expire_after` is reset. [#83134][#83134]
 - Removed the byte string parameter in the `crdb_internal.schedule_sql_stats_compaction` function. [#82560][#82560]
-- Changed the default value of the `enable_implicit_transaction_for_batch_statements` to `true`. This means that a [batch of statements]({% link v22.2/transactions.md %}#batched-statements) sent in one string separated by semicolons is treated as an implicit transaction. [#76834][#76834]
+- Changed the default value of the `enable_implicit_transaction_for_batch_statements` to `true`. This means that a [batch of statements](../v23.2/transactions.html#batched-statements) sent in one string separated by semicolons is treated as an implicit transaction. [#76834][#76834]

src/current/_includes/v23.2/sql/replication-zone-patterns-to-multiregion-sql-mapping.md

@@ -1,5 +1,5 @@
 | Replication Zone Pattern                         | Multi-Region SQL                                                                                                                                    |
 |--------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [Duplicate indexes]({% link v20.2/topology-duplicate-indexes.md %})                  | [`GLOBAL` tables]({% link {{ page.version.version }}/global-tables.md %})                                                                                                                       |
-| [Geo-partitioned replicas]({% link v20.2/topology-geo-partitioned-replicas.md %})        | [`REGIONAL BY ROW` tables]({% link {{ page.version.version }}/regional-tables.md %}#regional-by-row-tables) with [`ZONE` survival goals](multiregion-survival-goals.html#survive-zone-failures)     |
-| [Geo-partitioned leaseholders]({% link v20.2/topology-geo-partitioned-leaseholders.md %}) | [`REGIONAL BY ROW` tables]({% link {{ page.version.version }}/regional-tables.md %}#regional-by-row-tables) with [`REGION` survival goals](multiregion-survival-goals.html#survive-region-failures) |
+| Duplicate indexes (deprecated pattern)                  | [`GLOBAL` tables]({% link {{ page.version.version }}/global-tables.md %})                                                                                                                       |
+| Geo-partitioned replicas (deprecated pattern)        | [`REGIONAL BY ROW` tables]({% link {{ page.version.version }}/regional-tables.md %}#regional-by-row-tables) with [`ZONE` survival goals](multiregion-survival-goals.html#survive-zone-failures)     |
+| Geo-partitioned leaseholders (deprecated pattern) | [`REGIONAL BY ROW` tables]({% link {{ page.version.version }}/regional-tables.md %}#regional-by-row-tables) with [`REGION` survival goals](multiregion-survival-goals.html#survive-region-failures) |

src/current/_includes/v23.2/sql/show-ranges-output-deprecation-notice.md

@@ -5,7 +5,7 @@ The statement syntax and output documented on this page use the updated `SHOW RA
 SET CLUSTER SETTING sql.show_ranges_deprecated_behavior.enabled = true;
 ~~~
 
-The pre-v23.1 output of `SHOW RANGES` was deprecated in v23.1 and will be removed in a future release. To view the documentation for the deprecated version of the `SHOW RANGES` statement, see [`SHOW RANGES` (v22.2)]({% link v22.2/show-ranges.md %}).
+The pre-v23.1 output of `SHOW RANGES` was deprecated in v23.1 and will be removed in a future release. To view the documentation for the deprecated version of the `SHOW RANGES` statement, see the [archived version documentation]({% link releases/unsupported-versions.md %}).
 
 When you use the deprecated version of the `SHOW RANGES` statement, the following message will appear, reminding you to update [the cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}#setting-sql-show-ranges-deprecated-behavior-enabled):