docs: finalize v2.2.0 release

[AjayThorve]

Overview

Finalize the AI-Q v2.2.0 release documentation for the 2026-08-17 release.

• Mark v2.2.0 as released in the changelog and replace the release-candidate wording.
• Link the published NVIDIA NGC backend image, frontend image, and Helm chart at version 2.2.0.
• Correct the changelog's stale Helm chart version from 2.1.1 to 2.2.0.
• Surface the exact published artifact references in the repository README and deployment documentation.
• Refresh the tracked secrets baseline line metadata after the README update.

The package version, Docker Compose defaults, Helm chart metadata and values, and docs publisher metadata were already set to 2.2.0 on release/2.2 and remain unchanged.

DCO sign-off for the squash commit

Signed-off-by: Ajay Thorve athorve@nvidia.com
Signed-off-by: Ajay Thorve AjayThorve@users.noreply.github.com

Validation

• uv run --extra docs sphinx-build -M html docs/source docs/build

  • Passed; Sphinx built all 65 pages with three pre-existing unresolved cross-reference warnings.

• helm lint deploy/helm/deployment-k8s

  • Passed: 1 chart linted, 0 charts failed.

• pre-commit run --files .secrets.baseline CHANGELOG.md README.md docs/source/deployment/index.md

  • Passed all applicable hooks, including secret scanning and markdown link checking.

• Verified all three NVIDIA NGC v2.2.0 catalog URLs return HTTP 200.

• git verify-commit a1d74dc1eef848abcdcd95011474bddb0b408825

  • Good GPG signature from Ajay Thorve athorve@nvidia.com.

• I ran the relevant local checks or explained why they are not applicable.

• I added or updated tests for behavior changes. (Documentation-only release finalization; no behavior changed.)

• I updated documentation for user-facing or contributor-facing changes.

• I confirmed this PR does not include secrets, credentials, or internal-only data.

• I certify this contribution under the Developer Certificate of Origin (DCO) and signed my commits with git commit -s or an equivalent sign-off.

• I replaced the DCO sign-off placeholder with my GitHub commit identity and kept the required angle brackets around the email address.

Where should reviewers start?

Start with CHANGELOG.md, then verify the NGC artifact table in docs/source/deployment/index.md.

Related Issues

• None.

Summary by CodeRabbit

• New Release

  • Released AI-Q v2.2.0.
  • Published NVIDIA NGC artifacts for the backend container, frontend container, and Helm chart.

• Documentation

  • Added links and references for the v2.2.0 release artifacts.
  • Updated the changelog with categorized release highlights across deployment, integrations, observability, user experience, and workflow improvements.
  • Updated deployment documentation with installation references for the published containers and Helm chart.

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: ca6fffab-b26f-42b7-b6b8-8cf7dc9bfcc1

📥 Commits

Reviewing files that changed from the base of the PR and between 23df4c4 and a1d74dc.

📒 Files selected for processing (4)

• .secrets.baseline
• CHANGELOG.md
• README.md
• docs/source/deployment/index.md

Included review availability: Your plan includes up to 12 reviews per rolling hour; 11 remain after this review.

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (4)

**/*

📄 CodeRabbit inference engine (CONTRIBUTING.md)

**/*: Do not include secrets, credentials, private hostnames, internal-only logs, customer data, or generated local artifacts.
Add or update tests for behavior changes.

**/*: For substantial behavior, authentication, UI, or architecture changes, open a design discussion before coding rather than landing a large unreviewed change.
Keep changes scoped to this repository and avoid editing adjacent repositories; treat each sources/* package independently and prefer the smallest package-scoped change.
Keep pull requests scoped, avoid unrelated files and generated artifacts, provide validation evidence, and ensure every commit has DCO sign-off.

Files:

• README.md
• docs/source/deployment/index.md
• CHANGELOG.md

**/*.{py,pyi,js,jsx,ts,tsx,yml,yaml,json,env,md}

📄 CodeRabbit inference engine (AGENTS.md)

Never commit secrets, tokens, or environment-specific hostnames; use environment variables and SecretStr, and resolve API keys at runtime.

Files:

• README.md
• docs/source/deployment/index.md
• CHANGELOG.md

{docs/**,README.md,CONTRIBUTING.md,SECURITY.md,CODE-OF-CONDUCT.md}

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,SECURITY.md,CODE-OF-CONDUCT.md}: Review documentation for command accuracy, branch-name consistency, current CI and copy-pr-bot behavior, public
vs internal boundary clarity, stale examples, and links that no longer match the repository layout.

Files:

• README.md
• docs/source/deployment/index.md

docs/source/**/*

📄 CodeRabbit inference engine (AGENTS.md)

Update canonical documentation under docs/source/ when behavior, configuration, or workflows change; do not duplicate full documentation pages in skills.

Files:

• docs/source/deployment/index.md

🔇 Additional comments (4)

CHANGELOG.md (1)

3-9: LGTM!

Also applies to: 38-38

README.md (1)

101-106: LGTM!

.secrets.baseline (1)

136-136: LGTM!

Also applies to: 358-358

docs/source/deployment/index.md (1)

24-24: 🎯 Functional Correctness

Keep the NGC chart artifact reference.

nvidia/blueprint/aiq2-web:2.2.0 is used consistently in the release documentation. The Helm-installable .tgz URL is already documented in docs/source/deployment/kubernetes.md.

			> Likely an incorrect or invalid review comment.

---

Walkthrough

The PR finalizes the v2.2.0 release documentation, adds NVIDIA NGC references for published containers and the Helm chart, updates Helm metadata, and synchronizes the secret baseline with the README line change.

Changes

v2.2.0 release publication

Layer / File(s)	Summary
Published release artifact references CHANGELOG.md, README.md, docs/source/deployment/index.md	The release documentation now identifies the v2.2.0 backend container, frontend container, and Helm chart. The changelog updates the Helm chart metadata version to 2.2.0.
Secret baseline synchronization .secrets.baseline	The baseline updates the README finding to line 414 and refreshes its generation timestamp.

Estimated code review effort: 1 (Trivial) | ~4 minutes

Merge Risk: ⚪ Minimal · up to a1d74

The changes are limited to release documentation and tracked metadata, with no runtime behavior change; no actionable merge-blocking risk remains after normal checks.

Possibly related PRs

• NVIDIA-AI-Blueprints/aiq#322: Documents the earlier unreleased v2.2.0 candidate scope.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description includes all required sections, DCO sign-offs, validation details, reviewer guidance, and related-issue information.
Title check	✅ Passed	The title follows Conventional Commits format, uses an allowed lowercase type, states the release action, and meets the length rules.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[cdgamarose-nv]

lgtm

[AjayThorve]

/merge

[AjayThorve]

/ok to test a1d74dc

[AjayThorve]

/merge