Skip to content

docs(release-notes): add v3.12.2 and v3.11.8 release notes - #7957

Merged
jstirnaman merged 10 commits into
masterfrom
pbarnett/release-notes-3.12.2-3.11.8
Oct 29, 2026
Merged

jstirnaman merged 10 commits into
masterfrom
pbarnett/release-notes-3.12.2-3.11.8

Conversation

@peterbarnett03

Copy link
Copy Markdown
Collaborator

What changed

Adds v3.12.2 and v3.11.8 entries to the shared Core and Enterprise release notes, and updates the reference docs to match:

  • query-system-data: from v3.11.8 and v3.12.2, an ingest row in system.upgrade_parquet_node reads failed with the first unconvertible Parquet file in last_message.
  • influxdb3 manage retry-upgrade-to-pacha-tree: the command refuses to run while an ingest node lists Parquet files it could not convert.
  • data/products.yml: latest_patch moves from 3.12.0 to 3.12.2 for Core and Enterprise, for merge on the v3.12.2 release day.

Why

Sources in influxdb_pro:

  • v3.12.2: v3.12.1..1d56d74a85 on the 3.12 branch. Not tagged yet.
  • v3.11.8: v3.11.7..b67d65872c on the 3.11 branch. Not tagged yet.

Shared by both: the Python 3.13.18 bump, Core 429 for ResourcesExhausted (#6466), the table_deletion_status re-entrant lock (#6459), WAL plugin column binding (#6791), the node-stop registrant guard and fence (#6730, #6748), file index posting lists (#6461), one-pass version-tag reads (#6439), table index cache start (#6455), removed-generation details (#6462), gen0 write order on a restarted query node (#6441), and the storage engine upgrade fixes (#6417, #6528, #6693).

3.12 only: debug catalog repair backport (#6560), run-set pruning by column family (#5799), two-phase deduplication (#6144), stopping-ingester replication (#6764, #6777), Core-to-Enterprise catalog promotion (#6574), and the bounded runtime shutdown at exit (#6827). Enterprise already shut its runtime down in the background, so that bullet says so.

Left out of the notes: dependency advisories (rustls 0.23.46, wasmtime 48.0.7, ctutils 0.4.5, zstd-sys on 3.11, the emSign root, aws-sdk-s3 sigv4a), which change no product behavior; the planning-load count of unresolved output groups (#6202), whose effect is an internal admission limit; and CI, deny.toml, and lockfile alignment commits.

The Core 429 bullet differs between the two lines: 3.12 has the streamed-error fix (#6362) so CSV, JSON, and JSON Lines get the status when the query fails before the first rows; 3.11 does not, so only pretty and parquet output return 429 there.

Impact

The v3.12.2 and v3.11.8 dates (2026-10-29) are the planned release day. Both branch heads were fetched on 2026-10-28; commits after the documented refs would need a follow-up.

Verification

Each bullet was checked against source at the previous tag and the release ref, then reviewed adversarially by two independent passes. Those passes corrected three claims: a failed cluster upgrade is terminal, so the operator must run the retry command after restarting the node; the deleted-snapshot skip concerns Gen1 file cleanup, not compaction cleanup; and the table index cache bullet now states only the verified ordering change, not the connection-limit diagnosis from the commit message.
Vale (hooks' error level) passes on the changed files. yarn lint-codeblocks could not run locally (ERR_MODULE_NOT_FOUND); no code blocks were added. No Hugo build or link check was run.

Claude-Session: https://claude.ai/code/session_015hYwVhKpPRctfV6Eko1zV5

Closes #

What changed

Why

Impact

Verification

Checklist


Suggested reviewers (click to expand)

Based on files changed, consider requesting review from:

InfluxDB 3

Content Engineering Product
Core, Enterprise influxdata/monolith-team peterbarnett03, garylfowler
Clustered influxdata/platform-team ritwika314, sanderson
Cloud Dedicated influxdata/cloud-single-tenant ritwika314, sanderson
Cloud Serverless — mavarius, garylfowler
Explorer — mavarius, peterbarnett03

InfluxDB v2 / v1 / Enterprise v1

Content Engineering Product
v2, Cloud (TSM) influxdata/edge sanderson, jstirnaman
v1, Enterprise v1 influxdata/edge sanderson, jstirnaman

Other Products

Content Engineering Product
Telegraf influxdata/telegraf-team sanderson, caterryan
Kapacitor influxdata/bonitoo sanderson, jstirnaman
Chronograf influxdata/bonitoo mavarius, caterryan
Flux — sanderson, jstirnaman

Shared / Cross-Product

Content Reviewers
/content/shared/ influxdata/product-managers
API docs Relevant product team above

@peterbarnett03
peterbarnett03 requested a review from a team as a code owner October 29, 2026 02:18
@peterbarnett03
peterbarnett03 requested review from jstirnaman and sanderson and removed request for a team October 29, 2026 02:19
@github-actions

Copy link
Copy Markdown
Contributor

Vale Style Check Results

Metric Count
Errors 0
Warnings 2
Warnings (2)
File Line Rule Message
content/influxdb3/core/admin/query-system-data/_index.md 17 InfluxDataDocs.WordList Use 'administrator' instead of 'admin'.
content/influxdb3/enterprise/admin/query-system-data/_index.md 19 InfluxDataDocs.WordList Use 'administrator' instead of 'admin'.

✅ Check passed

@github-actions

Copy link
Copy Markdown
Contributor

Release version check

Product Release notes data/products.yml Status
influxdb3_core (latest_patch) 3.12.2 3.12.2 ✅ in sync
influxdb3_enterprise (latest_patch) 3.12.2 3.12.2 ✅ in sync

💡 Badge new features with the version

Documenting a new feature? Add a version badge in the page frontmatter — the
same mechanism used elsewhere in the docs:

  • metadata: [InfluxDB 3 Core v3.11+] — badge list under the page title
  • updated_in: v3.11 — an "Updated in v3.11" badge
  • introduced: v3.11 — a "‹Product› v3.11+" badge
  • menu.params.state: new — a "NEW" pill on the sidebar nav item

For inline version text, use {{< latest-patch >}} / {{< current-version >}},
which read the value from data/products.yml so it stays correct automatically.

@github-actions github-actions Bot added product:shared Shared content across products product:v3-monolith InfluxDB 3 Core and Enterprise (single-node / clusterable) labels Oct 29, 2026
@github-actions

github-actions Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

🔗 Link Check Results — Link Check Bot

✅ All links are valid

Metric Value
Files Checked 13
Total Links 5739
Errors 0
Warnings 22
Success Rate 99.28559%
⚠️ 22 warning(s) (do not fail CI)
Source File URL Issue
content/enterprise_influxdb/v1/introduction/installation/single-server/_index.md https://support.influxdata.com/ Error (cached): Error (cached)
content/enterprise_influxdb/v1/introduction/installation/single-server/_index.md https://reddit.com/r/influxdb Error (cached)
content/influxdb/v1/introduction/install/_index.md https://support.influxdata.com/ Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb/v2/install/_index.md https://support.influxdata.com/ Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb/v2/install/_index.md https://docs.docker.com/engine/reference/run/#detached-vs-foreground Cannot find fragment: Cannot find fragment
content/influxdb3/core/admin/query-system-data/_index.md https://support.influxdata.com/ Error (cached): Error (cached)
content/influxdb3/core/admin/query-system-data/_index.md https://reddit.com/r/influxdb Error (cached)
content/influxdb3/core/install/_index.md https://support.influxdata.com/ Error (cached): Error (cached)
content/influxdb3/core/install/_index.md https://reddit.com/r/influxdb Error (cached)
content/influxdb3/core/release-notes/_index.md https://support.influxdata.com/ Error (cached): Error (cached)
content/influxdb3/core/release-notes/_index.md https://reddit.com/r/influxdb Error (cached)
content/influxdb3/enterprise/admin/query-system-data/_index.md https://support.influxdata.com/ Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb3/enterprise/install/_index.md https://support.influxdata.com/ Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb3/enterprise/reference/cli/influxdb3/manage/retry-upgrade-to-pacha-tree/_index.md https://reddit.com/r/influxdb Error (cached)
content/influxdb3/enterprise/reference/cli/influxdb3/manage/retry-upgrade-to-pacha-tree/_index.md https://support.influxdata.com/ Error (cached): Error (cached)
content/influxdb3/enterprise/release-notes/_index.md https://reddit.com/r/influxdb Error (cached)
content/influxdb3/enterprise/release-notes/_index.md https://support.influxdata.com/ Error (cached): Error (cached)
content/influxdb3/explorer/install/_index.md https://support.influxdata.com/ Error (cached): Error (cached)
content/influxdb3/explorer/install/_index.md https://reddit.com/r/influxdb Error (cached)
content/telegraf/v1/install/_index.md https://support.influxdata.com/ Error (cached): Error (cached)

Showing first 20 of 22 warnings. See the workflow run for full results.


Full details: workflow run summary and artifact. Last updated: 2026-10-29 22:24:53 UTC

@sanderson sanderson left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor suggestion.

Comment thread content/shared/v3-core-enterprise-release-notes/_index.md Outdated
Comment thread content/shared/v3-core-enterprise-release-notes/_index.md Outdated
peterbarnett03 and others added 10 commits October 29, 2026 17:19
Adds v3.12.2 and v3.11.8 entries to the shared Core and Enterprise release
notes, and updates the reference docs to match:

- `query-system-data`: from v3.11.8 and v3.12.2, an `ingest` row in
  `system.upgrade_parquet_node` reads `failed` with the first unconvertible
  Parquet file in `last_message`.
- `influxdb3 manage retry-upgrade-to-pacha-tree`: the command refuses to run
  while an ingest node lists Parquet files it could not convert.
- `data/products.yml`: `latest_patch` moves from 3.12.0 to 3.12.2 for Core
  and Enterprise, for merge on the v3.12.2 release day.

Sources in influxdb_pro:

- v3.12.2: `v3.12.1..1d56d74a85` on the 3.12 branch. Not tagged yet.
- v3.11.8: `v3.11.7..b67d65872c` on the 3.11 branch. Not tagged yet.

Shared by both: the Python 3.13.18 bump, Core 429 for ResourcesExhausted
(#6466), the table_deletion_status re-entrant lock (#6459), WAL plugin
column binding (#6791), the node-stop registrant guard and fence (#6730,
(#6439), table index cache start (#6455), removed-generation details
(#6462), gen0 write order on a restarted query node (#6441), and the
storage engine upgrade fixes (#6417, #6528, #6693).

3.12 only: `debug catalog repair` backport (#6560), run-set pruning by
column family (#5799), two-phase deduplication (#6144), stopping-ingester
replication (#6764, #6777), Core-to-Enterprise catalog promotion (#6574),
and the bounded runtime shutdown at exit (#6827). Enterprise already shut
its runtime down in the background, so that bullet says so.

Left out of the notes: dependency advisories (rustls 0.23.46, wasmtime
48.0.7, ctutils 0.4.5, zstd-sys on 3.11, the emSign root, aws-sdk-s3
sigv4a), which change no product behavior; the planning-load count of unresolved output groups
(#6202), whose effect is an internal admission limit; and CI, deny.toml,
and lockfile alignment commits.

The Core 429 bullet differs between the two lines: 3.12 has the
streamed-error fix (#6362) so CSV, JSON, and JSON Lines get the status
when the query fails before the first rows; 3.11 does not, so only
`pretty` and `parquet` output return 429 there.

The v3.12.2 and v3.11.8 dates (2026-10-29) are the planned release day.
Both branch heads were fetched on 2026-10-28; commits after the documented
refs would need a follow-up.

Each bullet was checked against source at the previous tag and the
release ref, then reviewed adversarially by two independent passes.
Those passes corrected three claims: a `failed` cluster upgrade is
terminal, so the operator must run the retry command after restarting
the node; the deleted-snapshot skip concerns Gen1 file cleanup, not
compaction cleanup; and the table index cache bullet now states only the
verified ordering change, not the connection-limit diagnosis from the
commit message.
Vale (hooks' error level) passes on the changed files.
`yarn lint-codeblocks` could not run locally (ERR_MODULE_NOT_FOUND); no
code blocks were added. No Hugo build or link check was run.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015hYwVhKpPRctfV6Eko1zV5
What changed:
Remove the Core shutdown fix from the v3.12.2 notes, qualify the HTTP
streaming behavior by release line, add the complete ingest-failure retry
procedure, and apply semantic line feeds to the new release notes.

Why:
The shutdown fix at 1d56d74a85 is beyond the selected 3.12.2 candidate
3aeb9c30. Resetting a failed upgrade does not restart its compactor.
The 3.11 and 3.12 HTTP execution-error paths differ.

Impact:
Readers get release-scoped claims and an actionable recovery sequence.
Publication remains blocked on final tags, artifacts, and release approval.

Verification:
Hugo 0.156.0 full build, code-block lint, Vale at error level, and
staged diff whitespace checks passed. Checked five rendered consumers,
Enterprise-only upgrade guidance, and nine internal page/anchor targets.
All 32 new binary/checksum URLs returned 404; v3.12.1 controls returned
200. No live target-version product tests ran. Git hooks did not run;
this commit was created through the GitHub API.
What changed:
Add the remaining Core HTTP 500 caveat to v3.12.2 and v3.11.8.
Update the v3.12.2 source comment to the verified final tag.

Why:
Table deduplication can wrap memory exhaustion in an External error.
Phil reported this remaining case in influxdb_pro#6443.

Impact:
Preserves the streaming-response distinctions and Enterprise wording.

Verification:
Resolved v3.12.2 to f1972a0ff7 and compared it with 3aeb9c30e9.
Only the pulldown-cmark lockfile update was added.
Verified exactly three changed lines and preserved all existing bullet text.
Revert the file changes from 5bad339.
The reconciled corrections are now on Phil's PR #7961 so they can be
reviewed and merged as his contribution.

Verification:
Restores the exact file content from 43f045f.
…ill return 500

v3.12.2 is tagged at 3aeb9c30 plus #6990, so #6827 (1d56d74a85) is not in it. Smoke tests of both Core builds showed a GROUP BY on a table that exhausts memory during deduplication still returns 500.
Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com>
@jstirnaman
jstirnaman force-pushed the pbarnett/release-notes-3.12.2-3.11.8 branch from 912f381 to 6ce78fc Compare October 29, 2026 22:21
@jstirnaman
jstirnaman self-requested a review October 29, 2026 22:21
@jstirnaman
jstirnaman added this pull request to the merge queue Oct 29, 2026
Merged via the queue into master with commit b458fd2 Oct 29, 2026
27 checks passed
@jstirnaman
jstirnaman deleted the pbarnett/release-notes-3.12.2-3.11.8 branch October 29, 2026 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:shared Shared content across products product:v3-monolith InfluxDB 3 Core and Enterprise (single-node / clusterable)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants