In addition to the list of changes below, please also see theofficial release notes for other important information about this release.

v2.8.0 [2025/12/12]

Bug Fixes

1. 305e61d: Fix compilation on alpine linux

Features

1. 5e204dc: Add optional token hashing

Token Hashing

InfluxDB OSS 2.8.0 introduces token hashing. When activated using the --use-hashed-tokens, 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

It ishighly 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 isnever 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-hashed-tokens 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.

Other

1. 1e14c08: Update Go to 1.24.9
2. 40a6332: Updates post-install for linux package builds

The following are some highlighted updates with the newest release for InfluxDB 3 Core. Learn more via our fullRelease Notes.

Updates

Token Provisioning: You can now generate authentication tokens offline that can then be loaded up by the database at runtime if the tokens do not already exist, which works great for automated deployments and containerized environments. (#26734)

Azure Endpoint: You can now specify the Azure endpoint for object-store connections using the--azure-endpoint parameter (#26687)

No_Sync via CLI: The no_sync option can now be specified with the--no-sync parameter via the CLI on write commands (#26703)

Bug Fixes

• Tag and field names are validated when creating tables (#26641)
• Using GROUP BY twice on the same column no longer causes incorrect data (#26732)

Security & Misc

• Overly verbose TableIndexCache log is now quiet (#26709)
• WAL replay concurrency limit now defaults to number of CPU cores, preventing possible OOM (#26715)
• Unsafe signal_handler code removed (#26685)
• Python version upgraded to 3.13.7-20250818 (#26686,#26700)

Full Changelog:v3.3.0...v3.4.0

The following are some highlighted updates with the newest release for InfluxDB 3 Core. Learn more via our fullRelease Notes.

Updates

Authentication and security: Add admin token recovery server that allows regenerating lost admin tokens without existing authentication. Includes new--admin-token-recovery-http-bind option for running recovery server on separate port, with automatic shutdown after successful token regeneration (#26594)

Process Engine Trigger Arguments: You can access the trigger arguments for Process Engine triggers using thesystem.processing_engine_trigger_arguments table [#26604]

Passing git hash via env: Using environment variables, you can now pass the git hash in build.rs [#25266]

Fixes

Database reliability:

• Fix URL encoded table name handling failures (#26586)

• Allow hard deletion of existing soft-deleted schema (#26574)

Authentication: Fix AWS S3 API error handling when tokens are expired (#1013)

Query processing: Set nanosecond precision as default for V1 query API CSV output (#26577)

CLI reliability:

• Mark --object-store CLI argument as explicitly required (#26575)
• Add help text for the new update subcommand (#26569)

New Contributors

• @pfactum made their first contribution in#26618

Full Changelog:v3.2.1...v3.3.0

Contributors

Learn more via our fullRelease Notes.

Fixes

Operator tokens can no longer be deleted. [#26418]

Full Changelog:v3.0.2...v3.0.3

In addition to the list of changes below, please also see theofficial release notes for other important information about this release.

v2.7.12 [2025/05/15]

Bug Fixes

1. 9dc4b98: Defer calls that return a closure need to be called
2. eb1dd04: Prevent differing field types in the same shard

Features

1. 68534d3: Upgrade go to 1.23.5
2. 0d44e81: Improve dropped point logging
3. eb5acd8: TagValueIterator holds RLock for too long

Other

1. 1f9b96d: Chore: upgrade go toolchain to 1.22.11
2. 1fd7bd9: Build(flux): update flux to v0.196.1
3. e1bd5cd: Chore: use github.com/golang-jwt/jwt/v4 and update golang.org/x/net to v0.38.0
4. d6bc166: Chore: update to go 1.23.8
5. 601440b: Chore: update UI to OSS-v2.7.12
6. ec9dcde: Chore: update go to 1.23.9

Learn more via our fullRelease Notes.

Updates

JSON Format for Token Creation: Added support for --format json option in token creation command output. [#26286]
Dynamic TLS Certificate Generation: Added capability to generate testing TLS certificates on the fly. [#26288]
TLS Version Control: Added ability to set a minimum TLS version for enhanced security. [#26307]
CORS Support: Added support for CORS requests from browsers. [#26314]
Last Values Cache Improvements: Removed last cache size limitation for better performance. [#26333]

Fixes

Fixed counting bug in distinct cache. [#26332]
Fixed issue where distinct cache incorrectly handled rows with null values. [#26306]
Fixed handling of group by tag columns with escape quotes. [#26326]
Ensured consistent sorting of iox table schema for SHOW TABLES command. [#26302]

Full Changelog:v3.0.1...v3.0.2

v3.0.1 | 2015-04-16

Learn more via our fullRelease Notes.

Updates

• TLS CA can now be set with an environment variable:INFLUXDB3_TLS_CA
• Other general performance improvements

Fixes

• The--tags argument is now optional, and additionally now requires at least one tagif specified

v3.0.0 (2024-04-14)

Initial release of open source InfluxDB 3. Learn morehere.

In addition to the list of changes below, please also see the [official release notes] (https://docs.influxdata.com/influxdb/v2.7/reference/release-notes/influxdb/) for other important information about this release.

v2.7.11 [2024/11/26]

Bug Fixes

1. 46086c8: Add additional logging on loading fields.idxl files
2. 07df053: Fix data races in test code
3. 93d6ffc: Do not rename files on mmap failure

Features

1. 981f2fc: Add option to flush WAL on shutdown
2. e9ea8cf: Add--pid-file option to write PID files
3. 900e44d: Add startup logging for shard counts
4. 78e1d77: Check for uncommitted WRR segments during startup
5. aae5123: Adds log for rebuild TSI completion
6. 1b1f043: Upgrade go to 1.22.7
7. e3265b3: Upgrade go to 1.22.7
8. fbf5d4a: Merge branch '2.7' of github.com:influxdata/influxdb into 2.7

Other

1. cc9bd41: Chore: improve error messages and logging during shard opening
2. 7483bea: Chore: replace uses of %v with %w
3. f3d5325: Chore: upgrade ui assets package to 2.7.10
4. 941a41b: Chore: loadShards changes to more cleanly support 2.x feature

In addition to the list of changes below, please also see the [official release notes] (https://docs.influxdata.com/influxdb/v2.7/reference/release-notes/influxdb/) for other important information about this release.

v2.7.10 [2024/08/15]

Other

1. f302d97: Build(flux): update flux to v0.195.2