chore: Update docs

[ko3n1g]

What does this PR do ?

Add a one line overview of what this PR aims to accomplish.

Changelog

• Add specific line by line info of high level changes in this PR.

GitHub Actions CI

See the CI sectionin the Contributing doc for how to trigger the CI. A Nvidia developer will need to approve and trigger the CI for external contributors.

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you add or update any necessary documentation?
• Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  • Reviewer: Does the PR have correct import guards for all optional libraries?

If you haven't finished some of the above items you can still open "Draft" PR.

Additional Information

• Related to # (issue)

Summary by CodeRabbit

• Chores
  • Updated documentation version to 0.3.0 across configuration files.

[coderabbitai]

📝 Walkthrough

Walkthrough

These changes update documentation version references across multiple configuration files from "latest" to "0.3.0", adding a new version entry in the versions list while maintaining existing entries.

Changes

Cohort / File(s)	Summary
Documentation Version Updates docs/conf.py, docs/project.json, docs/versions1.json	Updated release version from "latest" to "0.3.0" in Sphinx configuration and project metadata. Added new version 0.3.0 entry in versions list, reordered to appear after "latest" and before "0.2.0", preserving existing version entries.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Suggested reviewers

• yaoyu-33
• ananthsub

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'chore: Update docs' is vague and generic, using non-descriptive language that fails to convey the specific nature of the changes made to documentation files.	Replace with a more specific title that describes the actual change, such as 'chore: Update docs to version 0.3.0' or 'chore: Update documentation release version to 0.3.0'.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Test Results For Major Changes	✅ Passed	PR contains only minor documentation and configuration changes (version updates in docs/conf.py, docs/project.json, and docs/versions1.json). No major functional changes, features, refactoring, or code modifications present.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ko3n1g/chore/update-docs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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