From cb63bf6ab7b66ffd6bca135c8676a57b93a01bac Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 13:58:42 -0600 Subject: [PATCH 01/15] feat: Add v2.8.0 release notes --- .../v2/reference/release-notes/influxdb.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index 2de95e4cec..ce76e85642 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -8,6 +8,21 @@ menu: weight: 101 --- +## v2.8.0 {date="2025-12-12"} + +### Features + +- [5e204dc](https://github.com/influxdata/influxdb/commit/5e204dc): Add optional token hashing + +### Bug Fixes + +- [305e61d](https://github.com/influxdata/influxdb/commit/305e61d): Fix compilation on alpine linux + +### Maintenance + +- [1b83d2c](https://github.com/influxdata/influxdb/commit/1b83d2c): Chore: update to go 1.23.12 (2.7) +- [40a6332](https://github.com/influxdata/influxdb/commit/40a6332): Updates post-install for linux package builds + ## v2.7.12 {date="2025-05-20"} ### Features From 9936d1d59ad030e59acfa3a299e52f13947b0efb Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 14:24:13 -0600 Subject: [PATCH 02/15] feat: add token hashing doc --- .../v2/reference/release-notes/influxdb.md | 38 +++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index ce76e85642..7e616b78d8 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -14,6 +14,44 @@ weight: 101 - [5e204dc](https://github.com/influxdata/influxdb/commit/5e204dc): Add optional token hashing +#### Token Hashing + +InfluxDB OSS 2.8.0 introduces token hashing. When activated using the --with-token-hashing, all API tokens are stored as hashes on disk. While token hashing is a valuable security upgrade, care should be taken when upgrading and enabling token hashing. + +Documentation link: [use-hashed-tokens](https://docs.influxdata.com/influxdb/v2/reference/config-options/#use-hashed-tokens) + + It is *highly* recommended to upgrade to 2.8.0 or later versions and enable hashed tokens in two steps, not one. + +#### How Token Hashing Works + +Upon upgrading to version 2.8.0 or later releases from version 2.7.12 or earlier releases, the BoltDB schema is upgraded to add a new index bucket. + +Upon startup when token hashing is enabled, all unhashed tokens are converted to hashed tokens and unhashed tokens are deleted. This check and conversion of unhashed tokens occurs on every startup when token hashing is enabled. + +When token hashing is disabled, any new tokens are stored as hashed tokens. If token hashing is disabled after being disabled, newly created tokens are stored unhashed. However, existing tokens remain hashed on disk. + +##### Hashed Tokens Are Lost During Downgrade + +Be aware that once token hashing is enabled, downgrading to a version earlier than 2.8.0 will erase all API tokens due to the required schema downgrade. This means downgrading requires recreating all API tokens and updating them on clients. Even if token hashing is disabled before downgrading, all API tokens will still need to be recreated because disabling token hashing does not unhash tokens stored in hashed form. + +If token hashing is *never* enabled, then it is possible to downgrade from 2.8.0 to 2.7.12 and earlier. + +##### Recommended Process + +It is not necessary to enabled token hashing immediately after upgrading. Token hashing is also not required by 2.8.0. + +1. Upgrade InfluxDB. + 1. Initiate influxd shutdown. + 2. Wait for a clean shutdown. + 3. Upgrade influxd. + 4. Start influxd. +2. Verify upgrade is successful. +3. Enable Token Hashing (if desired) + 1. Initiate influxd shutdown. + 2. Wait for a clean shutdown. + 3. Update configuration to use token hashing by adding --use-token-hashing to the command line or INFLUXD_USE_HASHED_TOKENS=true to the container environment. Or set use-hashed-tokens to true in the configuration file. + 4. Start influxd. + ### Bug Fixes - [305e61d](https://github.com/influxdata/influxdb/commit/305e61d): Fix compilation on alpine linux From 5d1c72db15656d4271a0ab7871b000c560bdf54a Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:16:12 -0600 Subject: [PATCH 03/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index 7e616b78d8..61eff8d602 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -16,7 +16,7 @@ weight: 101 #### Token Hashing -InfluxDB OSS 2.8.0 introduces token hashing. When activated using the --with-token-hashing, all API tokens are stored as hashes on disk. While token hashing is a valuable security upgrade, care should be taken when upgrading and enabling token hashing. +Introduces token hashing. When activated using the [`use-hashed-tokens` config option](/influxdb/v2/reference/config-options/#use-hashed-tokens), {{< product-name >}} stores all API tokens as hashes on disk. While token hashing is a valuable security upgrade, care should be taken when upgrading and enabling token hashing. Documentation link: [use-hashed-tokens](https://docs.influxdata.com/influxdb/v2/reference/config-options/#use-hashed-tokens) From edd3e8c8457cfa44e133d4a216e3e9a02424a7d9 Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:16:34 -0600 Subject: [PATCH 04/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index 61eff8d602..c03f031c66 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -20,7 +20,7 @@ Introduces token hashing. When activated using the [`use-hashed-tokens` config o Documentation link: [use-hashed-tokens](https://docs.influxdata.com/influxdb/v2/reference/config-options/#use-hashed-tokens) - It is *highly* recommended to upgrade to 2.8.0 or later versions and enable hashed tokens in two steps, not one. +If upgrading from earlier InfluxDB 2.x versions, we strongly recommend to upgrade to version 2.8.0 or later and then enable hashed tokens in two steps, not one. #### How Token Hashing Works From 9d28f5a1eb86ee4f27d3f1e48ee50bbebc6df9e4 Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:16:43 -0600 Subject: [PATCH 05/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index c03f031c66..87ff3576b9 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -24,7 +24,7 @@ If upgrading from earlier InfluxDB 2.x versions, we strongly recommend to upgrad #### How Token Hashing Works -Upon upgrading to version 2.8.0 or later releases from version 2.7.12 or earlier releases, the BoltDB schema is upgraded to add a new index bucket. +Upon upgrading to InfluxDB v2.8.0 or later from version 2.7.12 or earlier releases, the BoltDB schema is upgraded to add a new index bucket. Upon startup when token hashing is enabled, all unhashed tokens are converted to hashed tokens and unhashed tokens are deleted. This check and conversion of unhashed tokens occurs on every startup when token hashing is enabled. From 75e47efa00b8f2e625ab9a52ccc05ea3e3c2c055 Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:16:51 -0600 Subject: [PATCH 06/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index 87ff3576b9..e49fd6f54a 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -26,7 +26,7 @@ If upgrading from earlier InfluxDB 2.x versions, we strongly recommend to upgrad Upon upgrading to InfluxDB v2.8.0 or later from version 2.7.12 or earlier releases, the BoltDB schema is upgraded to add a new index bucket. -Upon startup when token hashing is enabled, all unhashed tokens are converted to hashed tokens and unhashed tokens are deleted. This check and conversion of unhashed tokens occurs on every startup when token hashing is enabled. +On every startup with token hashing enabled, InfluxDB 2.x migrates all unhashed tokens to hashed tokens and then deletes the unhashed tokens. When token hashing is disabled, any new tokens are stored as hashed tokens. If token hashing is disabled after being disabled, newly created tokens are stored unhashed. However, existing tokens remain hashed on disk. From 39d7be4550f11443707ddf201288e23d45e2724f Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:17:12 -0600 Subject: [PATCH 07/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index e49fd6f54a..6dc1cdc049 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -28,7 +28,7 @@ Upon upgrading to InfluxDB v2.8.0 or later from version 2.7.12 or earlier releas On every startup with token hashing enabled, InfluxDB 2.x migrates all unhashed tokens to hashed tokens and then deletes the unhashed tokens. -When token hashing is disabled, any new tokens are stored as hashed tokens. If token hashing is disabled after being disabled, newly created tokens are stored unhashed. However, existing tokens remain hashed on disk. +After you enable token hashing, any new tokens are stored as hashed tokens. If you then disable token hashing, newly created tokens are stored unhashed and existing tokens remain hashed on disk. ##### Hashed Tokens Are Lost During Downgrade From 43f0e138711250683ca437162dd3360178f35af7 Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:17:22 -0600 Subject: [PATCH 08/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index 6dc1cdc049..746dd3c10a 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -32,7 +32,7 @@ After you enable token hashing, any new tokens are stored as hashed tokens. If y ##### Hashed Tokens Are Lost During Downgrade -Be aware that once token hashing is enabled, downgrading to a version earlier than 2.8.0 will erase all API tokens due to the required schema downgrade. This means downgrading requires recreating all API tokens and updating them on clients. Even if token hashing is disabled before downgrading, all API tokens will still need to be recreated because disabling token hashing does not unhash tokens stored in hashed form. +Note that once token hashing is enabled, downgrading to a version earlier than 2.8.0 erases all API tokens due to the required schema downgrade. After downgrading, you'll need to create new tokens for your clients - even if you disable token hashing before you downgrade. Disabling token hashing **does not** unhash tokens stored in hashed form. If token hashing is *never* enabled, then it is possible to downgrade from 2.8.0 to 2.7.12 and earlier. From 83c64d8acce3408c06dfba8b0d785b78a966e614 Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:17:33 -0600 Subject: [PATCH 09/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index 746dd3c10a..f8ac84e508 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -38,7 +38,7 @@ If token hashing is *never* enabled, then it is possible to downgrade from 2.8.0 ##### Recommended Process -It is not necessary to enabled token hashing immediately after upgrading. Token hashing is also not required by 2.8.0. +You aren’t required to enable token hashing immediately after upgrading to InfluxDB v2.8.0. You can enable token hashing at any time after the upgrade. 1. Upgrade InfluxDB. 1. Initiate influxd shutdown. From 3eae5dc50d3531aedaffd900f2b9a2c8e2f27369 Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:17:43 -0600 Subject: [PATCH 10/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index f8ac84e508..aa7b494c7f 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -49,7 +49,10 @@ You aren’t required to enable token hashing immediately after upgrading to Inf 3. Enable Token Hashing (if desired) 1. Initiate influxd shutdown. 2. Wait for a clean shutdown. - 3. Update configuration to use token hashing by adding --use-token-hashing to the command line or INFLUXD_USE_HASHED_TOKENS=true to the container environment. Or set use-hashed-tokens to true in the configuration file. + 3. Do **one** of the following: + - Include the `--use-hashed-tokens` command line flag + - Set the `INFLUXD_USE_HASHED_TOKENS=true` environment variable in your container environment + - Set `use-hashed-tokens` to `true` in your configuration file 4. Start influxd. ### Bug Fixes From c1aa2e6f9d8949432efe6375b99c150ecd18e9a0 Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:17:52 -0600 Subject: [PATCH 11/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index aa7b494c7f..05b19e1ced 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -46,7 +46,7 @@ You aren’t required to enable token hashing immediately after upgrading to Inf 3. Upgrade influxd. 4. Start influxd. 2. Verify upgrade is successful. -3. Enable Token Hashing (if desired) +3. Optional: Enable token hashing 1. Initiate influxd shutdown. 2. Wait for a clean shutdown. 3. Do **one** of the following: From dc86d51e838498ae73516ea04a768b60da417748 Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:18:01 -0600 Subject: [PATCH 12/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index 05b19e1ced..17f93ee44b 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -57,7 +57,7 @@ You aren’t required to enable token hashing immediately after upgrading to Inf ### Bug Fixes -- [305e61d](https://github.com/influxdata/influxdb/commit/305e61d): Fix compilation on alpine linux +- [305e61d](https://github.com/influxdata/influxdb/commit/305e61d): Fix compilation on Alpine Linux ### Maintenance From da2aca537c5d5e633013a545236c6305b9e137aa Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:18:12 -0600 Subject: [PATCH 13/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index 17f93ee44b..8d642f60e1 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -62,7 +62,7 @@ You aren’t required to enable token hashing immediately after upgrading to Inf ### Maintenance - [1b83d2c](https://github.com/influxdata/influxdb/commit/1b83d2c): Chore: update to go 1.23.12 (2.7) -- [40a6332](https://github.com/influxdata/influxdb/commit/40a6332): Updates post-install for linux package builds +- [40a6332](https://github.com/influxdata/influxdb/commit/40a6332): Updates post-install for Linux package builds ## v2.7.12 {date="2025-05-20"} From f2c99745bac00a8c1e2d8babba7b0806ec7150f0 Mon Sep 17 00:00:00 2001 From: WeblWabl Date: Fri, 12 Dec 2025 16:18:22 -0600 Subject: [PATCH 14/15] feat: Update content/influxdb/v2/reference/release-notes/influxdb.md Co-authored-by: Jason Stirnaman --- content/influxdb/v2/reference/release-notes/influxdb.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index 8d642f60e1..c17650543e 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -18,7 +18,6 @@ weight: 101 Introduces token hashing. When activated using the [`use-hashed-tokens` config option](/influxdb/v2/reference/config-options/#use-hashed-tokens), {{< product-name >}} stores all API tokens as hashes on disk. While token hashing is a valuable security upgrade, care should be taken when upgrading and enabling token hashing. -Documentation link: [use-hashed-tokens](https://docs.influxdata.com/influxdb/v2/reference/config-options/#use-hashed-tokens) If upgrading from earlier InfluxDB 2.x versions, we strongly recommend to upgrade to version 2.8.0 or later and then enable hashed tokens in two steps, not one. From 146b6ea0e608d830e033b0af8a61d44b1f6d0a91 Mon Sep 17 00:00:00 2001 From: Jason Stirnaman Date: Fri, 12 Dec 2025 16:50:36 -0600 Subject: [PATCH 15/15] chore(influxdbv2): Revise release notes and bump version to 2.8.0. --- PLATFORM_REFERENCE.md | 2 +- .../v2/reference/release-notes/influxdb.md | 40 ++++++++++--------- data/products.yml | 6 +-- 3 files changed, 26 insertions(+), 22 deletions(-) diff --git a/PLATFORM_REFERENCE.md b/PLATFORM_REFERENCE.md index a0fc31afed..5cec041131 100644 --- a/PLATFORM_REFERENCE.md +++ b/PLATFORM_REFERENCE.md @@ -52,7 +52,7 @@ InfluxDB 3 Explorer: - Documentation: https://docs.influxdata.com/influxdb3/explorer/ Telegraf: - - Documentation: https://docs.influxdata.com/telegraf/v1.36/ + - Documentation: https://docs.influxdata.com/telegraf/v1.37/ Chronograf: - Documentation: https://docs.influxdata.com/chronograf/v1.10/ diff --git a/content/influxdb/v2/reference/release-notes/influxdb.md b/content/influxdb/v2/reference/release-notes/influxdb.md index c17650543e..94eaafcc7a 100644 --- a/content/influxdb/v2/reference/release-notes/influxdb.md +++ b/content/influxdb/v2/reference/release-notes/influxdb.md @@ -14,51 +14,55 @@ weight: 101 - [5e204dc](https://github.com/influxdata/influxdb/commit/5e204dc): Add optional token hashing -#### Token Hashing +#### Token hashing -Introduces token hashing. When activated using the [`use-hashed-tokens` config option](/influxdb/v2/reference/config-options/#use-hashed-tokens), {{< product-name >}} stores all API tokens as hashes on disk. While token hashing is a valuable security upgrade, care should be taken when upgrading and enabling token hashing. +Introduces token hashing. +When activated, token hashing stores all API tokens as hashes on disk. +While token hashing is a valuable security upgrade, care should be taken when upgrading and enabling token hashing. +Use the [`use-hashed-tokens`](/influxdb/v2/reference/config-options/#use-hashed-tokens) configuration option to enable token hashing in {{< product-name >}}. +If you are upgrading from an earlier InfluxDB 2.x version, we recommend first upgrading to version 2.8.0 (or later), and then enabling hashed tokens as a separate step. -If upgrading from earlier InfluxDB 2.x versions, we strongly recommend to upgrade to version 2.8.0 or later and then enable hashed tokens in two steps, not one. +Token hashing is optional and you can enable token hashing at any time after the upgrade. -#### How Token Hashing Works +#### How token hashing works Upon upgrading to InfluxDB v2.8.0 or later from version 2.7.12 or earlier releases, the BoltDB schema is upgraded to add a new index bucket. -On every startup with token hashing enabled, InfluxDB 2.x migrates all unhashed tokens to hashed tokens and then deletes the unhashed tokens. +On every startup with token hashing enabled, {{< product-name >}} migrates all unhashed tokens to hashed tokens and deletes the unhashed tokens. -After you enable token hashing, any new tokens are stored as hashed tokens. If you then disable token hashing, newly created tokens are stored unhashed and existing tokens remain hashed on disk. +With token hashing enabled, any new tokens are stored as hashed tokens. +If you then disable token hashing, newly created tokens are stored unhashed, but existing tokens remain hashed on disk. -##### Hashed Tokens Are Lost During Downgrade +##### Hashed tokens erased when downgrading -Note that once token hashing is enabled, downgrading to a version earlier than 2.8.0 erases all API tokens due to the required schema downgrade. After downgrading, you'll need to create new tokens for your clients - even if you disable token hashing before you downgrade. Disabling token hashing **does not** unhash tokens stored in hashed form. +Note that once token hashing is enabled, downgrading to a version earlier than 2.8.0 erases all API tokens due to the required schema downgrade. After downgrading, you'll need to create new tokens for your clients, even if you disable token hashing before you downgrade. Disabling token hashing **does not** unhash tokens stored in hashed form. -If token hashing is *never* enabled, then it is possible to downgrade from 2.8.0 to 2.7.12 and earlier. +If token hashing is _never_ enabled, then it is possible to downgrade from v2.8.0 to v2.7.12 and earlier. -##### Recommended Process - -You aren’t required to enable token hashing immediately after upgrading to InfluxDB v2.8.0. You can enable token hashing at any time after the upgrade. +##### Recommended process 1. Upgrade InfluxDB. 1. Initiate influxd shutdown. 2. Wait for a clean shutdown. 3. Upgrade influxd. 4. Start influxd. -2. Verify upgrade is successful. +2. Verify the upgrade is successful. 3. Optional: Enable token hashing 1. Initiate influxd shutdown. 2. Wait for a clean shutdown. - 3. Do **one** of the following: - - Include the `--use-hashed-tokens` command line flag - - Set the `INFLUXD_USE_HASHED_TOKENS=true` environment variable in your container environment - - Set `use-hashed-tokens` to `true` in your configuration file + 3. Do _one_ of the following: + - Include the `--use-hashed-tokens` command line flag + - Set the `INFLUXD_USE_HASHED_TOKENS=true` environment variable in your container environment + - Set `use-hashed-tokens` to `true` in your configuration file 4. Start influxd. + ### Bug Fixes - [305e61d](https://github.com/influxdata/influxdb/commit/305e61d): Fix compilation on Alpine Linux -### Maintenance +- [40a6332](https://github.com/influxdata/influxdb/commit/40a6332): Updates post-install for Linux package builds - [1b83d2c](https://github.com/influxdata/influxdb/commit/1b83d2c): Chore: update to go 1.23.12 (2.7) - [40a6332](https://github.com/influxdata/influxdb/commit/40a6332): Updates post-install for Linux package builds diff --git a/data/products.yml b/data/products.yml index b9d9c1042e..da3e30e522 100644 --- a/data/products.yml +++ b/data/products.yml @@ -177,12 +177,12 @@ influxdb: versions: - v2 - v1 - latest: v2.7 + latest: v2.8 latest_patches: - v2: 2.7.12 + v2: 2.8.0 v1: 1.12.2 latest_cli: - v2: 2.7.5 + v2: 2.8.0 detector_config: query_languages: InfluxQL: