File: content/manuals/ai/sandboxes/cloud/network-policy.md
Issue
The documentation contains a version-specific bug note that may be outdated:
Sandbox-specific policies remain in place and can still grant access. Inspect
those policies separately. In sbx version 0.42.0, the reset command prints
"reset to allow-all", but the service resets the account policy to deny-all.
This note describes a bug in version 0.42.0. According to the release notes, version 0.42.1 was released on 2026-09-07 (after 0.42.0), but the bug fix list in 0.42.1 does not mention whether this specific issue was resolved.
Why this matters
Readers using version 0.42.1 or later will be confused about whether this bug still affects them. Version-specific bug notes should either:
- Specify the version range where the bug exists (e.g., "In
sbx version 0.42.0 only" or "In versions 0.42.0 and earlier")
- Be removed if the bug was fixed in a subsequent release
Without clarification, users must guess whether the workaround still applies to their version.
Suggested fix
Verify whether the bug was fixed in version 0.42.1 or later. Then either:
- Update the note to specify the exact version range: "In
sbx version 0.42.0, the reset command prints..."
- Add a note that it was fixed: "This issue was fixed in version 0.42.1."
- Remove the note entirely if it no longer applies to any supported version
Found by nightly documentation quality scanner
File:
content/manuals/ai/sandboxes/cloud/network-policy.mdIssue
The documentation contains a version-specific bug note that may be outdated:
This note describes a bug in version 0.42.0. According to the release notes, version 0.42.1 was released on 2026-09-07 (after 0.42.0), but the bug fix list in 0.42.1 does not mention whether this specific issue was resolved.
Why this matters
Readers using version 0.42.1 or later will be confused about whether this bug still affects them. Version-specific bug notes should either:
sbxversion 0.42.0 only" or "In versions 0.42.0 and earlier")Without clarification, users must guess whether the workaround still applies to their version.
Suggested fix
Verify whether the bug was fixed in version 0.42.1 or later. Then either:
sbxversion 0.42.0, the reset command prints..."Found by nightly documentation quality scanner