Repository navigation
docs: remove the Public Preview label from docs, metadata and code - #4407
Open
MohammadHaroonAbuomar wants to merge 7 commits into
Open
MohammadHaroonAbuomar wants to merge 7 commits into
MohammadHaroonAbuomar wants to merge 7 commits into
Conversation
"Public Preview" is a product release stage. This repository is an MIT-licensed open-source project, not a product release, so the label does not apply and raised questions it could not answer (discussion #4326 asked for a GA date). Semver and BREAKING_CHANGES.md already say how API changes are handled. Remove the banner from README.md, the Spanish and Korean READMEs and the top of CHANGELOG.md, and update the roadmap's current-release line from v3.7.0 to v5.0.0, released 2026-06-25 per CHANGELOG.md and the v5.0.0 tag. Refs #4373 Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
Drop the "Public Preview" prefix from package descriptions in
package.json, pyproject.toml, Cargo.toml, .csproj and the Antigravity
extension manifest, and from package README headings and banners. The
label named a product release stage that does not apply to an MIT
open-source project. Sentences whose only content was the preview stage
("APIs may change before GA") are removed; factual notes such as the
Agent Learning version target stay.
Also drop the matching rule from .github/copilot-instructions.md and
the "Public Preview" kicker on the docs landing page, and correct the
JetBrains build comment: "IC" is IntelliJ IDEA Community.
Refs #4373
Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
Remove the "Public Preview" stage label from module headers, docstrings
and comments in agent-hypervisor, agent-mesh, agent-os (including the
caas and emk modules) and agent-sre, from pytest skip reasons, and from
the specs, tutorials and compliance docs that describe current
behaviour. Where a sentence said a feature is incomplete, the factual
part stays ("half-open recovery is not implemented", "elevation
requests are always denied") and only the label goes.
No behaviour or test assertion changes. No test asserted on the literal
string; the skip reasons now read "Feature not implemented". The
test_hash_chain_integrity docstring and the EU AI Act checklist item
that quoted a removed "no chain verification" comment are brought in
line with verify_chain(), which checks hashes and parent linkage.
Refs #4373
Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
scripts/ci/check_no_public_preview.sh fails when "public preview" appears in any tracked file outside the dated release history (CHANGELOG.md, BREAKING_CHANGES.md, docs/releases/). It runs from the repository root and prints each offending line. The script is not wired into quality-gates.yml here: that workflow is hand-written rather than generated from .github/ci/workflows.toml, so the PR notes the one job to add instead of editing it in this change. Also add the security audit note the existing gate requires because the module docstring of agent_os/mcp_gateway.py changed; the note records that no behaviour changed. Refs #4373 Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
Wire scripts/ci/check_no_public_preview.sh into the hand-written quality-gates.yml so the gate is enforced, widen its pattern to the hyphenated form and allow the dated dependency-audit records, and tighten the audit note to what was verified. Refs #4373 Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
MohammadHaroonAbuomar
requested review from
liamcrumm and
Prayag (prayagupa)
as code owners
October 21, 2026 06:40
github-actions
Bot
added
documentation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
github-actions
Bot
added
security
PR Review Summary
Verdict: AI review comments are untrusted advisory output. The summary reports workflow-generated completion status only, not model-authored pass/fail claims. |
📦 Dependency diff (SBOM)Comparing main → mhabuomar/issue-4373. ✅ No dependency changes detected. |
deepwiki.com answers the link checker with 429 and digital-strategy.ec.europa.eu with 403, so any PR that touches a page linking to them fails the check regardless of the change. Both links are valid in a browser. Add them to the ignore list. Refs #4373 Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
MohammadHaroonAbuomar
force-pushed
the
mhabuomar/issue-4373
branch
from
October 21, 2026 21:35
2b81478 to
bd1fdbc
Compare
github-actions
Bot
added
size/XL
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
Fixes #4373
Problem & Solution
The README, the roadmap, 22 package manifests, 20 package READMEs and docs pages, and about 60 source and test files carried a "Public Preview" label. That is a product release stage. This repository is an MIT open-source project, not a product release, so the label does not apply, and it raised questions it could not answer (discussion #4326 asked for a GA date). Semver and BREAKING_CHANGES.md already say how API changes are handled.
This PR removes the label everywhere it described the project's or a feature's stage:
verify_chain()now checks hashes and parent linkage.scripts/ci/check_no_public_preview.sh, which fails if the phrase returns outside the dated history.Kept as dated history: the 3.0.0 CHANGELOG entry, the BREAKING_CHANGES.md note that recorded why 5.0.0 could remove the hypervisor stubs, the shipped release notes under docs/releases, and four dated dependency-audit records. The guard allows those paths.
A short note under docs/security/audits is included because the security-audit gate fires on any change under
agent_os/mcp_gateway.py; only that module's docstring title changed.Impact on Your Work
None at runtime. Package descriptions on the registries lose the prefix on the next publish.
Timeline
None.
Alternatives Considered
Keeping the label with a definition of what it means. Rejected: the project is not on a product release track, and a definition would still invite the GA question.
Type of Change
Package(s) Affected
Testing
Run from the branch in a CI-like venv (editable core, integrations, CLI, protocols, agt-policies, native ACS SDK built with maturin):
pytest tests/: 663 passed, 23 skippedpytest tests/: 1595 passedpytest tests/: 4510 passed, 81 skippedpytest tests/: 3737 passed, 44 skippedruff check(E, F, W; E501 ignored) on all touched Python files: same findings as main, none newpython3 scripts/check_v4_ratchet.py: OKscripts/ci/changed_lines.py+ cspell 8.17.3): 0 issuesscripts/ci/check_no_public_preview.sh: passes on the branch, fails on mainAn independent verification pass re-ran the agent-hypervisor and agent-sre suites on main and on the branch with identical results, confirmed every Python hunk touches only comments, docstrings or skip reasons, and listed every remaining mention of the phrase against the rule above.
Checklist
Attribution
AI Assistance
Claude Code drafted the sweep under my direction; an independent verification pass re-checked every remaining mention, re-ran the package tests and the new guard, and I reviewed the result.
IP