You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Checklist**:
- [x] Add version key constant for new release (e.g. `V24_2`), equal to `Latest`.
Note that we do NOT update the `PreviousRelease` constant. We can only update the
`PreviousRelease` when an RC is published, which is needed for upgrade
roachtests.
- [x] Add final version for the previous release (e.g. `V24_1`).
- [x] Add start version (e.g. `V24_2_Start` with version `24.1-2`) and add a new
first upgrade for it (in `upgrades/upgrades.go`).
- [x] Update `SystemDatabaseSchemaBootstrapVersion` in
`pkg/sql/catalog/systemschema/system.go` to the start version just created.
- [x] Update `roachpb.successorSeries` map and update `TestReleaseSeriesSuccessor`
- [x] Update `pkg/build/version.txt` to the new version (e.g. `v24.2.0-alpha.00000000`)
- [x] Update the `scplan` rules in `pkg/sql/schemachanger/scplan/internal/rules`:
- copy the contents of `current` into a new release directory for the previous version
(e.g. `release_24_1`)
- change package name in all files (including `BUILD.bazel`), and update the
version in `current/helpers.go`
- update `rulesForReleases` in `scplan/plan.go`
- rewrite the test outputs: `./dev test pkg/sql/schemachanger/scplan/internal/rules/... --rewrite`
- rewrite `TestDeclarativeRules` output: `./dev test pkg/cli -f DeclarativeRules --rewrite`
- [x] Update releases file:
```
bazel build //pkg/cmd/release:release
_bazel/bin/pkg/cmd/release/release_/release update-releases-file
```
Note that the forked release version will disappear from the releases file. This
is what we want; if it is here, we will attempt to run upgrade tests against it.
- [x] Regenerate expected test data as needed (usually
`pkg/sql/catalog/systemschema_test` and some logictests).
Epic: none
Release note: None
Copy file name to clipboardExpand all lines: docs/generated/settings/settings-for-tenants.txt
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -411,4 +411,4 @@ trace.zipkin.collector string the address of a Zipkin instance to receive trace
411
411
ui.database_locality_metadata.enabled boolean true if enabled shows extended locality data about databases and tables in DB Console which can be expensive to compute application
412
412
ui.default_timezone string the default timezone used to format timestamps in the ui application
413
413
ui.display_timezone enumeration etc/utc the timezone used to format timestamps in the ui. This setting is deprecatedand will be removed in a future version. Use the 'ui.default_timezone' setting instead. 'ui.default_timezone' takes precedence over this setting. [etc/utc = 0, america/new_york = 1] application
414
-
version version 1000025.1-upgrading-to-1000025.2-step-008 set the active cluster version in the format '<major>.<minor>' application
414
+
version version 1000025.2-upgrading-to-1000025.3-step-002 set the active cluster version in the format '<major>.<minor>' application
Copy file name to clipboardExpand all lines: docs/generated/settings/settings.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -369,6 +369,6 @@
369
369
<tr><td><divid="setting-ui-database-locality-metadata-enabled" class="anchored"><code>ui.database_locality_metadata.enabled</code></div></td><td>boolean</td><td><code>true</code></td><td>if enabled shows extended locality data about databases and tables in DB Console which can be expensive to compute</td><td>Serverless/Dedicated/Self-Hosted</td></tr>
370
370
<tr><td><divid="setting-ui-default-timezone" class="anchored"><code>ui.default_timezone</code></div></td><td>string</td><td><code></code></td><td>the default timezone used to format timestamps in the ui</td><td>Serverless/Dedicated/Self-Hosted</td></tr>
371
371
<tr><td><divid="setting-ui-display-timezone" class="anchored"><code>ui.display_timezone</code></div></td><td>enumeration</td><td><code>etc/utc</code></td><td>the timezone used to format timestamps in the ui. This setting is deprecatedand will be removed in a future version. Use the 'ui.default_timezone' setting instead. 'ui.default_timezone' takes precedence over this setting. [etc/utc = 0, america/new_york = 1]</td><td>Serverless/Dedicated/Self-Hosted</td></tr>
372
-
<tr><td><divid="setting-version" class="anchored"><code>version</code></div></td><td>version</td><td><code>1000025.1-upgrading-to-1000025.2-step-008</code></td><td>set the active cluster version in the format '<major>.<minor>'</td><td>Serverless/Dedicated/Self-Hosted</td></tr>
372
+
<tr><td><divid="setting-version" class="anchored"><code>version</code></div></td><td>version</td><td><code>1000025.2-upgrading-to-1000025.3-step-002</code></td><td>set the active cluster version in the format '<major>.<minor>'</td><td>Serverless/Dedicated/Self-Hosted</td></tr>
select node_id, component, field, regexp_replace(regexp_replace(value, '^\d+$', '<port>'), e':\\d+', ':<port>') as value from crdb_internal.node_runtime_info
@@ -392,7 +392,7 @@ select * from crdb_internal.gossip_alerts
0 commit comments