Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[docs-scanner] Scout release notes use future tense for completed retirements

已关闭 适合新手
  • 哪里不对？
#26,211 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
90/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
docker
领域
documentation

调研方向

打开 content/manuals/scout/release-notes/platform.md，并将 2026-07-01 的条目与之后 2026-07-30 和 2026-09-01 的停用条目进行比较。更新或删除较早的弃用通知，使发布说明准确描述已完成的停用，不再暗示这些停用仍在等待处理。

由索引模型根据 Issue 内容生成。

描述

File: content/manuals/scout/release-notes/platform.md

Issue

The Q2 2026 section (dated 2026-07-01) describes feature retirements using future tense, even though later entries in the same document confirm these retirements have already occurred:

The following is deprecated and will be retired on July 30, 2026:

  • Slack integration: Vulnerability and policy compliance notifications to Slack channels.

The following are deprecated and will be retired on September 1, 2026:

  • Notifications: In-product and email notifications about newly disclosed CVEs.
  • Amazon ECR integration: Automatically analyzed images pushed to ECR registries.
  • Azure Container Registry integration: Automatically analyzed images pushed to ACR registries.
  • Policies page in the Dashboard: Provided a visual interface in the Docker Scout Dashboard for tracking policy compliance.
  • SonarQube integration.

However, the document's own later entries (2026-07-30 and 2026-09-01) confirm these features were retired:

2026-07-30

The following Docker Scout feature was retired:

  • Slack integration: Integrate docker scout cves or docker scout policy into your CI pipeline...
2026-09-01

The following Docker Scout features were retired:

  • Notifications: In-product and email notifications about newly disclosed CVEs.
  • Native Amazon ECR integration: ECR is still supported using [docker scout watch]...
  • Native Azure Container Registry integration: ACR is still supported using the same options as ECR.
  • Policies page in the Dashboard: The docker scout policy command replaces this...
  • SonarQube integration.
Why this matters

Readers consulting the release notes to understand the current state of Docker Scout features will be confused by the 2026-07-01 entry saying features "will be retired" on dates that have already passed. This makes it unclear whether these features are currently available or not, forcing readers to scan through the entire document to reconcile the conflicting statements.

Suggested fix

Update the 2026-07-01 entry to use past tense and clarify that these deprecation notices were announcements made at that time, with the actual retirements occurring later. For example:

The following feature was announced for retirement on July 30, 2026 (retired as of that date):

  • Slack integration

The following features were announced for retirement on September 1, 2026 (retired as of that date):

  • Notifications
  • Amazon ECR integration
  • Azure Container Registry integration
  • Policies page in the Dashboard
  • SonarQube integration

Alternatively, consider removing the 2026-07-01 deprecation notices entirely since the actual retirement entries (2026-07-30 and 2026-09-01) provide the complete information readers need.

Found by nightly documentation quality scanner

主要语言
Markdown
星标
4.7k
派生
8.5k
平均合并
1 天 18 小时
30 天内合并 PR
127

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

docker/docs 的其他 Issue

查看 docker/docs 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。