[docs-scanner] Version-specific bug note may be stale in cloud network-policy.md

Open Beginner friendly
#26,053 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Start with content/manuals/ai/sandboxes/cloud/network-policy.md and check the sbx 0.42.1 release notes for whether the reset-policy bug was fixed. Update or remove the version-specific note based on that verification, or state the exact affected version range, and confirm the resulting guidance is unambiguous for supported versions.

Written by the indexing model from the issue text.

Description

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:

  1. 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")
  2. 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

Dominant language
Markdown
Stars
4.7k
Forks
8.5k
Avg merge
2d 12h
Merged PRs (30d)
104

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/docs

All issues in docker/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.