fix(v1): publish OSS v1.12.3, defer Enterprise v1.12.3 pending GA by jstirnaman · Pull Request #6945 · influxdata/docs-v2

jstirnaman · 2026-03-14T18:16:36Z

Summary

Reverts the combined InfluxDB 1.12.3 release commit (InfluxDB 1.12.3 release #6872) that published both OSS and Enterprise docs simultaneously
Re-adds only OSS v1.12.3 documentation (release notes, config options, InfluxQL spec fixes)
Updates v1 release tooling (agent, PR template, command) to enforce separate OSS/Enterprise PRs going forward

Enterprise v1.12.2 docs fixes are in a separate PR to be merged after this one.
Enterprise v1.12.3 documentation is in a separate draft PR, pending GA in the portal.

Changes

Content (OSS v1 only)

content/influxdb/v1/about_the_project/release-notes.md — v1.12.3 release notes
content/influxdb/v1/administration/config.md — https-insecure-certificate and advanced-expiration config options
content/influxdb/v1/query_language/manage-database.md — FUTURE/PAST LIMIT clause order fix
content/influxdb/v1/query_language/spec.md — InfluxQL spec cleanup + ordering caution for pre-v1.12.3 users
data/products.yml — OSS version bump only (1.12.2 → 1.12.3); Enterprise stays at 1.12.2

Tooling

.claude/agents/influxdb1-tech-writer.md — added release documentation workflow section
.github/pull_request_template/influxdb_v1_release.md — separate OSS/Enterprise PRs, Enterprise pre-merge gate
.claude/commands/prepare-release-notes.md — v1 release workflow with separate PR examples

Test plan

Hugo build succeeds (npx hugo --quiet)
No Enterprise v1 content changes in diff
data/products.yml shows OSS at 1.12.3, Enterprise at 1.12.2
Link validation passes for OSS v1 content

This reverts commit 14e021a.

…g GA Revert the combined InfluxDB 1.12.3 release commit and re-add only OSS v1.12.3 documentation. Enterprise v1.12.3 docs will be published in a separate PR once the release artifact is GA in the portal. Also adds FUTURE/PAST LIMIT ordering caution for users on versions prior to v1.12.3 (from copilot/restore-ordering-warning-influxql).

Update the influxdb1-tech-writer agent, v1 release PR template, and prepare-release-notes command to enforce the practice of always creating separate PRs for OSS v1 and Enterprise v1 releases. Enterprise must wait for GA in the portal before merging.

github-actions · 2026-03-14T18:18:48Z

PR Preview Action v1.4.8
🚀 Deployed preview to https://influxdata.github.io/docs-v2/pr-preview/pr-6945/
on branch `gh-pages` at 2026-03-14 20:04 UTC

github-actions · 2026-03-14T18:19:58Z

Preview Pages for Review

6 page(s) changed in this PR:

Preview URLs

@github-copilot please review the preview pages listed above using the template below:

Visual Review Prompt

Review the rendered documentation pages at the preview URLs listed below.
Check each page for visual and structural issues that are invisible in the
Markdown source.

Checklist

For each preview URL, verify:

No raw shortcodes — No {{< or {{% syntax visible on the page
No placeholder text — No PLACEHOLDER, TODO, FIXME, or
template variables visible in rendered content
Layout intact — No overlapping text, missing images, or collapsed
sections
Code blocks render correctly — No raw HTML fences or Markdown
syntax visible inside code blocks
Product names correct — Page header, breadcrumbs, and sidebar show
the correct product name
No 404s or errors — Page loads without error states
Navigation correct — Sidebar entries link to the right pages and
the page appears in the expected location

Output

Follow the shared review comment format, severity definitions, and label
mapping in
templates/review-comment.md.

Adapt the "Files Reviewed" section to list preview URLs instead of file
paths.

Preview URLs

jstirnaman

@davidby-influx Can you review the note in content/influxdb/v1/query_language/spec.md?
Enterprise content is restored to 1.12.2.

…luxQL spec The revert of the combined v1.12.3 commit removed grammar production definitions (retention_future_limit, retention_past_limit) that document existing InfluxQL syntax, not v1.12.3-specific features. Restore them so the grammar is complete.

…s in InfluxQL spec" This reverts commit c497f13.

davidby-influx

Some reversions should not occur. Apologies.

davidby-influx · 2026-03-14T19:10:31Z

content/enterprise_influxdb/v1/query_language/manage-database.md


 ```sql
-CREATE DATABASE <database_name> [WITH [DURATION <duration>] [REPLICATION <n>] [SHARD DURATION <duration>] [FUTURE LIMIT <duration>] [PAST LIMIT <duration>] [NAME <retention-policy-name>]]
+CREATE DATABASE <database_name> [WITH [DURATION <duration>] [REPLICATION <n>] [SHARD DURATION <duration>] [PAST LIMIT <duration>] [FUTURE LIMIT <duration>] [NAME <retention-policy-name>]]


Correct syntax is the FUTURE LIMIT PAST LIMIT in that order, so I think this fix should stand.

Will fix in a separate PR

content/enterprise_influxdb/v1/query_language/manage-database.md

davidby-influx · 2026-03-14T19:14:58Z

content/enterprise_influxdb/v1/query_language/spec.md

+>non-string field values in the
+>`WHERE` clause,
+>[databases](/enterprise_influxdb/v1/concepts/glossary/#database), and
+>[retention polices](/enterprise_influxdb/v1/concepts/glossary/#retention-policy-rp).


Typo, should be "policies"

Separate PR

davidby-influx · 2026-03-14T19:21:55Z

content/enterprise_influxdb/v1/query_language/manage-database.md

 for recommended configurations.

-##### `FUTURE LIMIT` {metadata="v1.12.0+"}
+##### `PAST LIMIT` {metadata="v1.12.0+"}


As above, leave the correction.

davidby-influx · 2026-03-14T19:24:27Z

content/enterprise_influxdb/v1/query_language/manage-database.md

+The `ALTER RETENTION POLICY` query takes the following form, where you must declare at least one of the retention policy attributes `DURATION`, `REPLICATION`, `SHARD DURATION`, or `DEFAULT`:
 ```sql
-ALTER RETENTION POLICY <retention_policy_name> ON <database_name> [DURATION <duration>] [REPLICATION <n>] [SHARD DURATION <duration>] [FUTURE LIMIT <duration>] [PAST LIMIT <duration>] [DEFAULT]
+ALTER RETENTION POLICY <retention_policy_name> ON <database_name> [DURATION <duration>] [REPLICATION <n>] [SHARD DURATION <duration>] [DEFAULT]


I would leave the previous syntax that includes FUTURE and PAST

davidby-influx · 2026-03-14T19:26:10Z

content/enterprise_influxdb/v1/query_language/spec.md

-- specify the duration, future and past limits, and name of that retention policy
-CREATE DATABASE "bar" WITH DURATION 1d FUTURE LIMIT 6h PAST LIMIT 6h NAME "myrp"
+-- specify the duration, past and future limits, and name of that retention policy
+CREATE DATABASE "bar" WITH DURATION 1d PAST LIMIT 6h FUTURE LIMIT 6h NAME "myrp"


Previous syntax, FUTURE, PAST order is correct

Prior bug, will fix in a separate PR

davidby-influx · 2026-03-14T19:26:34Z

content/enterprise_influxdb/v1/query_language/spec.md

-- Create a retention policy and specify future and past limits.
-CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 12h FUTURE LIMIT 6h PAST LIMIT 6h
+-- Create a retention policy and specify past and future limits.
+CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 12h PAST LIMIT 6h FUTURE LIMIT 6h


Previous order, FUTURE, PAST is correct.

Prior bug - will fix in a separate PR

davidby-influx · 2026-03-14T19:31:06Z

content/influxdb/v1/query_language/spec.md

 > When using both `FUTURE LIMIT` and `PAST LIMIT` clauses, `FUTURE LIMIT` must appear before `PAST LIMIT`.

+> [!Caution]
+> **Prior to InfluxDB v1.12.3**, when using both `FUTURE LIMIT` and `PAST LIMIT` clauses,


I believe this is incorrect. Syntax is FUTURE, PAST; 1.12.3 fixes Enterprise meta-node recording of the limits, but not the syntax

OK, I see. There was a previous docs bug that had them reversed and I translated it to an actual syntax bug.

davidby-influx · 2026-03-14T19:33:53Z

content/influxdb/v1/query_language/spec.md

 > [!Note]
 > When using both `FUTURE LIMIT` and `PAST LIMIT` clauses, `FUTURE LIMIT` must appear before `PAST LIMIT`.

+> [!Caution]


Order is FUTURE, PAST, but 1.12.3 fixes a bug that caused retention of the limits in Enterprise to fail silently.

… spec The caution stated that prior to v1.12.3, PAST LIMIT must appear before FUTURE LIMIT. This is incorrect — the correct syntax has always been FUTURE LIMIT before PAST LIMIT. The v1.12.3 fix addresses Enterprise meta-node recording of limits, not parser syntax order.

jstirnaman

👍 Reverts enterprise changes completely. Pre-existing bugs will be fixed separately. Enterprise v1.12.3 docs will be released separately upon GA.

jstirnaman · 2026-03-14T20:05:24Z

content/enterprise_influxdb/v1/query_language/spec.md

+>non-string field values in the
+>`WHERE` clause,
+>[databases](/enterprise_influxdb/v1/concepts/glossary/#database), and
+>[retention polices](/enterprise_influxdb/v1/concepts/glossary/#retention-policy-rp).


Separate PR

jstirnaman · 2026-03-14T20:06:44Z

content/enterprise_influxdb/v1/query_language/spec.md

-- specify the duration, future and past limits, and name of that retention policy
-CREATE DATABASE "bar" WITH DURATION 1d FUTURE LIMIT 6h PAST LIMIT 6h NAME "myrp"
+-- specify the duration, past and future limits, and name of that retention policy
+CREATE DATABASE "bar" WITH DURATION 1d PAST LIMIT 6h FUTURE LIMIT 6h NAME "myrp"


Prior bug, will fix in a separate PR

jstirnaman · 2026-03-14T20:07:20Z

content/enterprise_influxdb/v1/query_language/spec.md

-- Create a retention policy and specify future and past limits.
-CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 12h FUTURE LIMIT 6h PAST LIMIT 6h
+-- Create a retention policy and specify past and future limits.
+CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 12h PAST LIMIT 6h FUTURE LIMIT 6h


Prior bug - will fix in a separate PR

jstirnaman added 3 commits March 14, 2026 13:01

Revert "InfluxDB 1.12.3 release (#6872)"

85ea926

This reverts commit 14e021a.

jstirnaman requested a review from a team as a code owner March 14, 2026 18:16

jstirnaman requested review from sanderson and removed request for a team March 14, 2026 18:16

github-actions bot added product:v1 InfluxDB v1 OSS product:v1-enterprise InfluxDB Enterprise v1 labels Mar 14, 2026

jstirnaman mentioned this pull request Mar 14, 2026

feat(enterprise): InfluxDB Enterprise v1.12.3 release #6946

Closed

6 tasks

jstirnaman added the release/v1 InfluxDB v1 OSS/Enterprise release documentation label Mar 14, 2026

jstirnaman commented Mar 14, 2026

View reviewed changes

jstirnaman added 2 commits March 14, 2026 13:52

Revert "fix(enterprise): restore FUTURE/PAST LIMIT grammar production…

3f6b969

…s in InfluxQL spec" This reverts commit c497f13.

davidby-influx requested changes Mar 14, 2026

View reviewed changes

jstirnaman commented Mar 14, 2026

View reviewed changes

jstirnaman merged commit a3dbf2e into master Mar 14, 2026
9 of 10 checks passed

github-actions bot added a commit that referenced this pull request Mar 14, 2026

Clean up preview for PR #6945

06cb68d

Conversation

jstirnaman commented Mar 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Content (OSS v1 only)

Tooling

Test plan

Uh oh!

github-actions bot commented Mar 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Mar 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Preview Pages for Review

Visual Review Prompt

Checklist

Output

Preview URLs

Uh oh!

jstirnaman left a comment

Choose a reason for hiding this comment

Uh oh!

davidby-influx left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jstirnaman left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

jstirnaman commented Mar 14, 2026 •

edited

Loading

github-actions bot commented Mar 14, 2026 •

edited

Loading

github-actions bot commented Mar 14, 2026 •

edited

Loading