Skip to content

docs: remove alpha software references#4590

Merged
ericksoa merged 3 commits into
mainfrom
chore/remove-alpha-software-mentions
Jun 1, 2026
Merged

docs: remove alpha software references#4590
ericksoa merged 3 commits into
mainfrom
chore/remove-alpha-software-mentions

Conversation

@ericksoa
Copy link
Copy Markdown
Contributor

@ericksoa ericksoa commented Jun 1, 2026

Summary

  • remove the alpha software note and status-alpha badge from the README
  • remove the alpha software announcement from the Fern docs config
  • remove the status-alpha badge from the docs landing page
  • update AGENTS.md status wording from Alpha to Active development

Validation

  • git diff --check
  • npm run docs:strict
  • FERN_VERSION=$(node -p "require('./fern/fern.config.json').version") && cd fern && npx --yes "fern-api@${FERN_VERSION}" check --warnings

Fern check reports 0 errors. The 2 warnings are the pre-existing unauthenticated redirects check and light-mode accent contrast warning.

Summary by CodeRabbit

  • Documentation
    • Project status updated from “Alpha” to “Active development” across documentation.
    • Removed alpha warning banners and site announcement messaging.
    • Updated repository badges and introductory header to include a Discord join badge alongside existing badges.

Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 1, 2026

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7572778e-475e-4eaa-ba8a-f76d0b88ee71

📥 Commits

Reviewing files that changed from the base of the PR and between 8861ee0 and 83ae329.

📒 Files selected for processing (1)
  • AGENTS.md
✅ Files skipped from review due to trivial changes (1)
  • AGENTS.md

📝 Walkthrough

Walkthrough

This PR removes alpha project status indicators and updates repository status to "Active development" across AGENTS.md, README badges, docs/index.mdx badge links, and fern/docs.yml site announcement.

Changes

Repository Status Transition

Layer / File(s) Summary
Remove alpha status indicators
AGENTS.md, README.md, docs/index.mdx, fern/docs.yml
Agent instructions status line updated to "Active development"; README badges row now includes Discord and omits the alpha Project Status badge and NOTE block; docs/index.mdx badges array no longer includes the Project Status entry; fern/docs.yml announcement/banner block removed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • NVIDIA/NemoClaw#4552: Overlapping documentation updates to landing/status badges and docs index entries.

Suggested labels

documentation

Suggested reviewers

  • cv

Poem

🐰 From alpha nights to active light,
The badges changed and banners flight,
Docs refreshed with brighter cheer,
The repo hops into the clear.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: remove alpha software references' directly and accurately summarizes the main change: removing alpha software status indicators and messages across multiple documentation files.
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.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/remove-alpha-software-mentions

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • None. No E2E jobs are recommended because this PR is documentation/site-content only and cannot affect NemoClaw runtime behavior, installer/onboarding, sandbox lifecycle, credentials, security boundaries, network policy, inference routing, deployment logic, or real assistant user flows. Docs build/preview checks may be appropriate in regular CI, but existing runtime E2E coverage is not needed for this change.

Optional E2E

  • None.

New E2E recommendations

  • None.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

E2E Scenario Advisor Recommendation

Required scenario E2E: None
Optional scenario E2E: None

Workflow run

Full scenario advisor summary

E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required scenario E2E

  • None. Docs and repository guidance/configuration changes only; no files under test/e2e-scenario/, scenario workflows, or directly scenario-relevant runtime/catalog paths were changed.

Optional scenario E2E

  • None.

Relevant changed files

  • None.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@AGENTS.md`:
- Line 10: Replace the Markdown-emphasized status line "**Status:** Active
development. Interfaces may change without notice." with the exact canonical
plain text "Status: Active development. Interfaces may change without notice." —
locate the current status string in AGENTS.md (the line starting with
"**Status:**") and update it to the exact required wording without any Markdown
emphasis or punctuation changes.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: d7e3d487-d2f7-480e-abc9-5692c5f2fee1

📥 Commits

Reviewing files that changed from the base of the PR and between 9641ce0 and 2d09ad3.

📒 Files selected for processing (4)
  • AGENTS.md
  • README.md
  • docs/index.mdx
  • fern/docs.yml
💤 Files with no reviewable changes (3)
  • README.md
  • fern/docs.yml
  • docs/index.mdx

Comment thread AGENTS.md Outdated
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

PR Review Advisor

Findings: 0 needs attention, 2 worth checking, 0 nice ideas
Since last review: 0 prior items resolved, 2 still apply, 0 new items found

Review findings

🛠️ Needs attention

  • None.

🔎 Worth checking

  • Source-of-truth review needed: Project maturity and production-suitability documentation: The advisor marked localized patch analysis as needs_followup.
    • Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
    • Evidence: README.md, docs/index.mdx, and fern/docs.yml remove alpha/non-production warnings; AGENTS.md now says Active development; docs/about/release-notes.mdx still says NemoClaw is available in early preview starting March 16, 2026.
  • Align canonical maturity and production-suitability messaging before dropping public warnings (README.md:10): The PR removes the README alpha badge and non-production note, the docs landing status badge, and the Fern global announcement that said not to use NemoClaw in production. For a sandbox/security-oriented project, this can weaken user risk perception if NemoClaw is still early-preview or not production-suitable. Nearby source-of-truth wording is still not aligned because the release notes continue to say NemoClaw is available in early preview.
    • Recommendation: Confirm the authoritative product/release decision for NemoClaw maturity and production suitability. If NemoClaw is still early-preview or not production-ready, keep scoped public warning language while removing only the alpha label if needed. If NemoClaw is production-suitable, update remaining public status sources such as release notes so the docs are consistent.
    • Evidence: Diff removes README status-alpha badge and note saying NemoClaw is alpha software and not production-ready; removes docs/index.mdx Project Status badge; removes fern/docs.yml announcement saying alpha software and Do not use in production; changes AGENTS.md to Status: Active development. docs/about/release-notes.mdx still says: NVIDIA NemoClaw is available in early preview starting March 16, 2026.

🌱 Nice ideas

  • None.
Since last review details

Current findings:

  • Source-of-truth review needed: Project maturity and production-suitability documentation: The advisor marked localized patch analysis as needs_followup.
    • Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
    • Evidence: README.md, docs/index.mdx, and fern/docs.yml remove alpha/non-production warnings; AGENTS.md now says Active development; docs/about/release-notes.mdx still says NemoClaw is available in early preview starting March 16, 2026.
  • Align canonical maturity and production-suitability messaging before dropping public warnings (README.md:10): The PR removes the README alpha badge and non-production note, the docs landing status badge, and the Fern global announcement that said not to use NemoClaw in production. For a sandbox/security-oriented project, this can weaken user risk perception if NemoClaw is still early-preview or not production-suitable. Nearby source-of-truth wording is still not aligned because the release notes continue to say NemoClaw is available in early preview.
    • Recommendation: Confirm the authoritative product/release decision for NemoClaw maturity and production suitability. If NemoClaw is still early-preview or not production-ready, keep scoped public warning language while removing only the alpha label if needed. If NemoClaw is production-suitable, update remaining public status sources such as release notes so the docs are consistent.
    • Evidence: Diff removes README status-alpha badge and note saying NemoClaw is alpha software and not production-ready; removes docs/index.mdx Project Status badge; removes fern/docs.yml announcement saying alpha software and Do not use in production; changes AGENTS.md to Status: Active development. docs/about/release-notes.mdx still says: NVIDIA NemoClaw is available in early preview starting March 16, 2026.

Workflow run details

This is an automated advisory review. A human maintainer must make the final merge decision.

Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
@ericksoa ericksoa self-assigned this Jun 1, 2026
Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
@ericksoa ericksoa merged commit 4e89db9 into main Jun 1, 2026
30 checks passed
@ericksoa ericksoa deleted the chore/remove-alpha-software-mentions branch June 1, 2026 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants