- Restructure content flow to follow progressive disclosure principles
- Move index type decision to Important callout after basic upgrade steps
- Improve headings with active voice ("Switch index types anytime")
- Enhance callout formatting (Important, Tip, Warning callouts)
- Consolidate Enterprise upgrade information into dedicated section
- Improve information hierarchy and scanability
Changes are primarily formatting and phrasing improvements to enhance
developer experience and follow Google Developer Documentation best practices.
- Make TSI recommendation more actionable by explaining benefits (removes RAM limits, better performance for high-cardinality data)
- Fix "from to" grammar typos in index switching instructions
- Add specific scenarios for when to switch between TSI and inmem index types
- Remove "above" directional language per style guidelines
Source: Verified against InfluxDB v1 documentation via MCP docs verification
- TSI details: https://docs.influxdata.com/influxdb/v1/concepts/tsi-details/
- TSI overview: https://docs.influxdata.com/influxdb/v1/concepts/time-series-index/
Addresses customer confusion where scaling CPU alone doesn't improve
compactor performance. Compactor concurrency scales based on memory
allocation, not CPU count, so both resources should be scaled together.
Closesinfluxdata/DAR#514
add related links
chore(ci): Replaced PR link validation workflow with new workflow from docs-tooling/link-checker/.github-workflows-link-check.yml
chore: organize .gitignore
test: add content to trigger link-checker workflow
This small change tests the pr-link-check.yml workflow
feat: update link-checker workflow and documentation
- Add production config with corrected User-Agent placement
- Remove old link validation actions (replaced by link-checker)
fix: update link-checker workflow configuration
- Update Node.js version to 20 for dependency compatibility
feat: use pre-built link-checker binary from docs-tooling releases
- Replace building from source with downloading from releases
- Use GitHub API to get latest release and binary
- Maintain same artifact structure for downstream job
fix: improve change detection in pr-link-check workflow
- Use GitHub API for reliable PR file detection
- Add debug output to show all changed files
- Fix conditional logic for when jobs should run
docs: update TESTING.md with binary distribution and automated GitHub Actions integration
- Document pre-built binary download as recommended installation method
- Explain automated PR link checking workflow for docs-v2
- Replace manual GitHub Actions example with automated integration details
- Remove exaggerated language and specify actual exclusion types
fix(ci): download link-checker binary from docs-v2 releases
- Change binary source from private docs-tooling to public docs-v2 releases
- Fixes GitHub Actions permission issues accessing private repos
- Binary is now stored as a release asset on docs-v2 itself
test: add test file with valid links to verify workflow passes
test: remove temporary test file for link checker workflow
The test file was only needed to verify the workflow functionality
and should not be part of the documentation.
docs: update TESTING.md to document docs-v2 binary distribution
- Change primary installation method to download from docs-v2 releases
- Explain that binary distribution enables reliable GitHub Actions access
- Update automated workflow description to reflect docs-v2 release usage
- Maintain build-from-source as alternative option
refactor(ci): combine workflow into single job for cleaner PR display
- Merge detect-changes, build-site, and download-link-checker into single job
- All setup steps now run conditionally within one job
- Cleaner PR display shows only 'Check links in affected files'
- Maintains all functionality with improved UX
fix(ci): exclude problematic URLs from link checking
- Add reddit.com exclusions (blocks bots)
- Add support.influxdata.com exclusion (SSL certificate issues in CI)
- Prevents false positive failures in automated link checking
**Revert this commit for the v1.12 release**\
- Remove links from release notes to upcoming 1.12.x features
- Add callout to explain that v1.12 isn't yet available
**Keep this commit for the upcoming v1.12 release**
- Label upcoming features as v1.12.0+:
- Update configuration documentation for data nodes
- Update database management documentation
- Update influx_inspect tool documentation
- Update show-shards documentation
- Revert product version references to 1.11.8 in products.yml