Skip to content

build(release): autoPublish 改回 true - #48

Merged
im47cn merged 1 commit into
mainfrom
im47cn/snaggletooth
Nov 17, 2026
Merged

im47cn merged 1 commit into
mainfrom
im47cn/snaggletooth

Conversation

@im47cn

@im47cn im47cn commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

变更

  • pom.xml 的 central-publishing 配置 autoPublish false → true:Portal 校验通过即自动发布,去掉每版人工 Portal 环节
  • 同步过时注释/文档:release.yml 步骤名、CONTRIBUTING.md §8、docs/release-guide.md §2.1/§5

依据

  • 0.1.0(2026-08-31)、0.2.0(2026-09-18)均已走通人工 Publish 链路,"仅首次"策略已到期
  • 发布不可撤销、坐标永久公开 → 风险控制点前移到推 tag 前

验证

  • mvn -P release validate 通过(XML + profile 解析)
  • release.yml YAML 解析通过

Sourcery 摘要

在 Portal 验证成功后自动发布到 Maven Central,并使发布指南与新的不可撤销发布流程保持一致。

增强功能:

  • 在 Portal 验证后启用自动发布到 Maven Central,从 0.3.0 版本起不再需要常规的手动发布步骤。
  • 更新发布流程指南和文档,以反映不可撤销的自动发布流程,以及在打标签前验证版本的必要性。

文档:

  • 更新发布文档、贡献者指南、工作流提示信息和发布报告,以落实自动发布政策。
Original summary in English

Summary by Sourcery

Enable automatic Maven Central publishing after successful Portal validation and align release guidance with the new irreversible publication workflow.

Enhancements:

  • Enable automatic Maven Central publication after Portal validation, removing the routine manual publishing step from version 0.3.0 onward.
  • Update release workflow guidance and documentation to reflect the irreversible automatic publication process and the need to verify versions before tagging.

Documentation:

  • Refresh release documentation, contributor guidance, workflow messaging, and release reports for the automatic publishing policy.

- 0.1.0/0.2.0 已验证人工 Publish 链路,无需每版人工闸
- 同步 pom 注释、release.yml 步骤名、CONTRIBUTING §8、release-guide §2.1/§5
@changeset-bot

changeset-bot Bot commented Nov 17, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2bc19d0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Nov 17, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 481720fd-c2ab-46bf-bcab-976910019664
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@sourcery-ai

sourcery-ai Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

审阅者指南

配置

在 Portal 验证通过后启用 Maven Central 自动发布,并更新发布工作流步骤的说明,以体现发布操作不可撤销。

  • .github/workflows/release.yml L101-102
  • pom.xml L221-222

文档

更新贡献指南和发布指南,说明从 0.3.0 版本开始自动发布,并将发布风险检查移至推送标签之前。

  • CONTRIBUTING.md L126
  • docs/release-guide.md L68-78(另有 3 处小改动)
  • docs/wop-sdk-report-java.md L219

提示与命令

与 Sourcery 交互

  • 触发新一轮审查: 在拉取请求中评论 @sourcery-ai review。
  • 继续讨论: 直接回复 Sourcery 的审查评论。
  • 根据审查评论创建 GitHub issue: 回复审查评论,请 Sourcery 根据该评论创建 issue。你也可以在审查评论下回复 @sourcery-ai issue,以此创建 issue。
  • 生成拉取请求标题: 在拉取请求标题的任意位置写入 @sourcery-ai,即可随时生成标题。你也可以在拉取请求中评论 @sourcery-ai title,以重新生成标题。
  • 生成拉取请求摘要: 在拉取请求正文中你希望放置摘要的位置写入 @sourcery-ai summary,即可随时生成摘要。你也可以在拉取请求中评论 @sourcery-ai summary,以重新生成摘要。
  • 生成审阅者指南: 在拉取请求中评论 @sourcery-ai guide,即可随时重新生成审阅者指南。
  • 解决所有 Sourcery 评论: 在拉取请求中评论 @sourcery-ai resolve,即可解决所有 Sourcery 评论。如果你已处理完所有评论且不想再看到它们,这个命令会很有用。
  • 忽略所有 Sourcery 审查: 在拉取请求中评论 @sourcery-ai dismiss,即可忽略所有现有的 Sourcery 审查。如果你想从头开始进行新一轮审查,这个命令尤其有用——别忘了评论 @sourcery-ai review 来触发新一轮审查!

自定义使用体验

访问你的控制面板以:

  • 启用或停用审查功能,例如由 Sourcery 生成的拉取请求摘要、审阅者指南等。
  • 更改审查语言。
  • 添加、移除或编辑自定义审查说明。
  • 调整其他审查设置。

获取帮助

Original review guide in English

Reviewer's Guide

Configuration

Enable automatic Maven Central publication after Portal validation and update the release workflow step description to reflect the irreversible publish behavior.

  • .github/workflows/release.yml L101-102
  • pom.xml L221-222

Documentation

Update contributor and release guidance to document automatic publishing from 0.3.0 onward and move the release-risk check to before pushing a tag.

  • CONTRIBUTING.md L126
  • docs/release-guide.md L68-78 (+3 small edits)
  • docs/wop-sdk-report-java.md L219

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

嗨——我发现了 5 个问题

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="pom.xml" line_range="222" />
<code_context>
-              <!-- 首次发版策略:false = 上传后停在 Portal 待发布,人工核对后手动 Publish -->
-              <autoPublish>false</autoPublish>
+              <!-- 链路上线策略:true = Portal 校验通过后自动发布(发布不可撤销,坐标永久公开) -->
+              <autoPublish>true</autoPublish>
             </configuration>
           </plugin>
</code_context>
<issue_to_address>
**Unapproved artifacts publish publicly**

When a matching `v*` tag points to an unintended or malicious commit that passes `mvn verify`, the release workflow checks only the tag-to-POM version and `mvn verify`, then `autoPublish=true` publishes the tagged artifacts without a human approval checkpoint, so unapproved or malicious artifacts become public.

Require explicit human approval before publishing tagged release artifacts instead of auto-publishing them.
</issue_to_address>

### Comment 2
<location path="pom.xml" line_range="222" />
<code_context>
-              <!-- 首次发版策略:false = 上传后停在 Portal 待发布,人工核对后手动 Publish -->
-              <autoPublish>false</autoPublish>
+              <!-- 链路上线策略:true = Portal 校验通过后自动发布(发布不可撤销,坐标永久公开) -->
+              <autoPublish>true</autoPublish>
             </configuration>
           </plugin>
</code_context>
<issue_to_address>
**Local deploy bypasses release gate**

When a maintainer runs the release-profile deploy command locally with Central credentials configured, a developer running `mvn -P release deploy` outside GitHub Actions activates this same release profile and automatically publishes the current checkout, without the workflow’s tag/version check; a local or untagged build can therefore consume a permanent Central version before the reviewed release.

Make automatic publishing opt-in via a property set only by the guarded release workflow, or otherwise enforce the workflow’s release checks for every invocation.
</issue_to_address>

### Comment 3
<location path="pom.xml" line_range="222" />
<code_context>
-              <!-- 首次发版策略:false = 上传后停在 Portal 待发布,人工核对后手动 Publish -->
-              <autoPublish>false</autoPublish>
+              <!-- 链路上线策略:true = Portal 校验通过后自动发布(发布不可撤销,坐标永久公开) -->
+              <autoPublish>true</autoPublish>
             </configuration>
           </plugin>
</code_context>
<issue_to_address>
**Retagged release publishes stale artifacts**

When a version tag is deleted and repushed to a different commit while the original release job is still running, the original job can publish its checked-out commit through `autoPublish=true`, permanently occupying the version; the newer run is then rejected and the older artifacts remain public.

Cancel in-flight release jobs when a tag is retargeted and gate upload on the tag still pointing to the job’s checked-out commit.

Also at `docs/release-guide.md:78-79`.
</issue_to_address>

### Comment 4
<location path="docs/release-guide.md" line_range="77-78" />
<code_context>

-> **不可撤回提醒**:Central 发布后坐标永久公开、不可删除。发布前发现的任何问题,
-> 直接在 Portal 丢弃(Discard)该部署,修完重新打 tag(删除 tag 重推即可,workflow 幂等)。
+> **不可撤回提醒**:Central 发布后坐标永久公开、不可删除。上传前发现的任何问题,
+> 直接丢弃(Discard)该部署,修完重新打 tag(删除 tag 重推即可,workflow 幂等)。

 ## 3. 阶段三:发版后验证
</code_context>
<issue_to_address>
**Discard guidance cannot stop release**

When an operator finds a release issue before upload and follows the discard instruction, the guide directs operators to discard a deployment that does not yet exist; after upload, `autoPublish=true` publishes it as soon as validation passes, leaving no discard window to stop an erroneous release.

Replace the discard-and-retag recovery instruction with guidance that reflects there is no deployment to discard before upload and no discard window after automatic publication.
</issue_to_address>

### Comment 5
<location path="docs/wop-sdk-report-java.md" line_range="219" />
<code_context>
 | 测试/覆盖率 | 208 tests 全绿;聚合行/分支 100.00% |

-**已按用户决策修正**:`autoPublish` true→false(首次发版人工核对后手动 Publish);release.yml 注释验证路径改为 DNS TXT(原注释写的 GitHub 仓库验证不适用于 com.wanlianyida)。
+**已按用户决策修正**:`autoPublish` true→false(首次发版人工核对后手动 Publish);release.yml 注释验证路径改为 DNS TXT(原注释写的 GitHub 仓库验证不适用于 com.wanlianyida)。(0.3.0 起改回 `true`,见 CONTRIBUTING §8)

 **发版前唯一阻断项**:Central Portal namespace `com.wanlianyida` 的 DNS TXT 验证(需 wanlianyida.com 域名控制权,操作指引见会话回复)。
</code_context>
<issue_to_address>
**Release instructions contradict each other**

When a maintainer consults the report to understand the current release process, `docs/wop-sdk-report-java.md` says releases require manual Publish and refers to `autoPublish=false`, while the release guide says Portal validation publishes automatically, so readers get conflicting instructions.

Update the report’s release-policy description and reference to match the current automatic-publishing process.

Also at `docs/release-guide.md:70`.
</issue_to_address>

Sourcery 评估

需要人工审核。 有 4 项发现需要先处理;并且启用 autoPublish=true 后,通过 Portal 验证的带标签版本会在没有人工审核环节的情况下永久公开。回滚可以为未来的版本恢复人工把关,但无法撤回已经发布的制品;自动发布策略本身才是影响重大的决策。

阻塞性发现:pom.xml:222、pom.xml:222、pom.xml:222、docs/release-guide.md:78


Sourcery 对开源项目免费——如果你喜欢我们的评审,请考虑分享 ✨
Original comment in English

Hey - I've found 5 issues

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="pom.xml" line_range="222" />
<code_context>
-              <!-- 首次发版策略:false = 上传后停在 Portal 待发布,人工核对后手动 Publish -->
-              <autoPublish>false</autoPublish>
+              <!-- 链路上线策略:true = Portal 校验通过后自动发布(发布不可撤销,坐标永久公开) -->
+              <autoPublish>true</autoPublish>
             </configuration>
           </plugin>
</code_context>
<issue_to_address>
**Unapproved artifacts publish publicly**

When a matching `v*` tag points to an unintended or malicious commit that passes `mvn verify`, the release workflow checks only the tag-to-POM version and `mvn verify`, then `autoPublish=true` publishes the tagged artifacts without a human approval checkpoint, so unapproved or malicious artifacts become public.

Require explicit human approval before publishing tagged release artifacts instead of auto-publishing them.
</issue_to_address>

### Comment 2
<location path="pom.xml" line_range="222" />
<code_context>
-              <!-- 首次发版策略:false = 上传后停在 Portal 待发布,人工核对后手动 Publish -->
-              <autoPublish>false</autoPublish>
+              <!-- 链路上线策略:true = Portal 校验通过后自动发布(发布不可撤销,坐标永久公开) -->
+              <autoPublish>true</autoPublish>
             </configuration>
           </plugin>
</code_context>
<issue_to_address>
**Local deploy bypasses release gate**

When a maintainer runs the release-profile deploy command locally with Central credentials configured, a developer running `mvn -P release deploy` outside GitHub Actions activates this same release profile and automatically publishes the current checkout, without the workflow’s tag/version check; a local or untagged build can therefore consume a permanent Central version before the reviewed release.

Make automatic publishing opt-in via a property set only by the guarded release workflow, or otherwise enforce the workflow’s release checks for every invocation.
</issue_to_address>

### Comment 3
<location path="pom.xml" line_range="222" />
<code_context>
-              <!-- 首次发版策略:false = 上传后停在 Portal 待发布,人工核对后手动 Publish -->
-              <autoPublish>false</autoPublish>
+              <!-- 链路上线策略:true = Portal 校验通过后自动发布(发布不可撤销,坐标永久公开) -->
+              <autoPublish>true</autoPublish>
             </configuration>
           </plugin>
</code_context>
<issue_to_address>
**Retagged release publishes stale artifacts**

When a version tag is deleted and repushed to a different commit while the original release job is still running, the original job can publish its checked-out commit through `autoPublish=true`, permanently occupying the version; the newer run is then rejected and the older artifacts remain public.

Cancel in-flight release jobs when a tag is retargeted and gate upload on the tag still pointing to the job’s checked-out commit.

Also at `docs/release-guide.md:78-79`.
</issue_to_address>

### Comment 4
<location path="docs/release-guide.md" line_range="77-78" />
<code_context>

-> **不可撤回提醒**:Central 发布后坐标永久公开、不可删除。发布前发现的任何问题,
-> 直接在 Portal 丢弃(Discard)该部署,修完重新打 tag(删除 tag 重推即可,workflow 幂等)。
+> **不可撤回提醒**:Central 发布后坐标永久公开、不可删除。上传前发现的任何问题,
+> 直接丢弃(Discard)该部署,修完重新打 tag(删除 tag 重推即可,workflow 幂等)。

 ## 3. 阶段三:发版后验证
</code_context>
<issue_to_address>
**Discard guidance cannot stop release**

When an operator finds a release issue before upload and follows the discard instruction, the guide directs operators to discard a deployment that does not yet exist; after upload, `autoPublish=true` publishes it as soon as validation passes, leaving no discard window to stop an erroneous release.

Replace the discard-and-retag recovery instruction with guidance that reflects there is no deployment to discard before upload and no discard window after automatic publication.
</issue_to_address>

### Comment 5
<location path="docs/wop-sdk-report-java.md" line_range="219" />
<code_context>
 | 测试/覆盖率 | 208 tests 全绿;聚合行/分支 100.00% |

-**已按用户决策修正**:`autoPublish` true→false(首次发版人工核对后手动 Publish);release.yml 注释验证路径改为 DNS TXT(原注释写的 GitHub 仓库验证不适用于 com.wanlianyida)。
+**已按用户决策修正**:`autoPublish` true→false(首次发版人工核对后手动 Publish);release.yml 注释验证路径改为 DNS TXT(原注释写的 GitHub 仓库验证不适用于 com.wanlianyida)。(0.3.0 起改回 `true`,见 CONTRIBUTING §8)

 **发版前唯一阻断项**:Central Portal namespace `com.wanlianyida` 的 DNS TXT 验证(需 wanlianyida.com 域名控制权,操作指引见会话回复)。
</code_context>
<issue_to_address>
**Release instructions contradict each other**

When a maintainer consults the report to understand the current release process, `docs/wop-sdk-report-java.md` says releases require manual Publish and refers to `autoPublish=false`, while the release guide says Portal validation publishes automatically, so readers get conflicting instructions.

Update the report’s release-policy description and reference to match the current automatic-publishing process.

Also at `docs/release-guide.md:70`.
</issue_to_address>

Sourcery assessment

Needs a human reviewer. 4 findings to address first, and with autoPublish=true, a tagged release that passes Portal validation becomes permanently public without a human review step. Reverting can restore the manual gate for future releases, but cannot withdraw artifacts already published; the automatic-publication policy itself is the consequential decision.

Blocking findings: pom.xml:222, pom.xml:222, pom.xml:222, docs/release-guide.md:78


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread pom.xml
<!-- 首次发版策略:false = 上传后停在 Portal 待发布,人工核对后手动 Publish -->
<autoPublish>false</autoPublish>
<!-- 链路上线策略:true = Portal 校验通过后自动发布(发布不可撤销,坐标永久公开) -->
<autoPublish>true</autoPublish>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟠 高 · 未经批准的制品会公开发布

当匹配的 v* 标签指向意外或恶意的提交,且该提交通过 mvn verify 时,发布工作流只检查标签与 POM 版本是否匹配以及 mvn verify 是否通过,随后 autoPublish=true 就会在没有人工审批环节的情况下发布带标签的制品,因此未经批准或恶意的制品会公开发布。

应在发布带标签的版本制品前要求明确的人工审批,而不是自动发布。

提供给 AI 智能体的提示
在 `pom.xml` 第 222 行:

**未经批准的制品会公开发布**

当匹配的 `v*` 标签指向意外或恶意的提交,且该提交通过 `mvn verify` 时,发布工作流只检查标签与 POM 版本是否匹配以及 `mvn verify` 是否通过,随后 `autoPublish=true` 就会在没有人工审批环节的情况下发布带标签的制品,因此未经批准或恶意的制品会公开发布。

应在发布带标签的版本制品前要求明确的人工审批,而不是自动发布。
Original comment in English

🟠 High · Unapproved artifacts publish publicly

When a matching v* tag points to an unintended or malicious commit that passes mvn verify, the release workflow checks only the tag-to-POM version and mvn verify, then autoPublish=true publishes the tagged artifacts without a human approval checkpoint, so unapproved or malicious artifacts become public.

Require explicit human approval before publishing tagged release artifacts instead of auto-publishing them.

Prompt for AI agents
In `pom.xml` at line 222:

**Unapproved artifacts publish publicly**

When a matching `v*` tag points to an unintended or malicious commit that passes `mvn verify`, the release workflow checks only the tag-to-POM version and `mvn verify`, then `autoPublish=true` publishes the tagged artifacts without a human approval checkpoint, so unapproved or malicious artifacts become public.

Require explicit human approval before publishing tagged release artifacts instead of auto-publishing them.

Comment thread pom.xml
<!-- 首次发版策略:false = 上传后停在 Portal 待发布,人工核对后手动 Publish -->
<autoPublish>false</autoPublish>
<!-- 链路上线策略:true = Portal 校验通过后自动发布(发布不可撤销,坐标永久公开) -->
<autoPublish>true</autoPublish>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 中 · 本地部署绕过发布关卡

当维护者配置了 Central 凭据并在本地运行发布配置的部署命令时,开发者在 GitHub Actions 之外运行 mvn -P release deploy,会激活同一个发布配置并自动发布当前检出的代码,而不会执行工作流中的标签/版本检查;因此,本地构建或未打标签的构建可能会在经过审核的版本发布之前占用一个永久性的 Central 版本号。

通过仅由受保护的发布工作流设置的属性来选择启用自动发布,或者以其他方式确保每次调用都执行工作流中的发布检查。

提供给 AI 智能体的提示
在 `pom.xml` 第 222 行:

**本地部署绕过发布关卡**

当维护者配置了 Central 凭据并在本地运行发布配置的部署命令时,开发者在 GitHub Actions 之外运行 `mvn -P release deploy`,会激活同一个发布配置并自动发布当前检出的代码,而不会执行工作流中的标签/版本检查;因此,本地构建或未打标签的构建可能会在经过审核的版本发布之前占用一个永久性的 Central 版本号。

通过仅由受保护的发布工作流设置的属性来选择启用自动发布,或者以其他方式确保每次调用都执行工作流中的发布检查。
Original comment in English

🟡 Medium · Local deploy bypasses release gate

When a maintainer runs the release-profile deploy command locally with Central credentials configured, a developer running mvn -P release deploy outside GitHub Actions activates this same release profile and automatically publishes the current checkout, without the workflow’s tag/version check; a local or untagged build can therefore consume a permanent Central version before the reviewed release.

Make automatic publishing opt-in via a property set only by the guarded release workflow, or otherwise enforce the workflow’s release checks for every invocation.

Prompt for AI agents
In `pom.xml` at line 222:

**Local deploy bypasses release gate**

When a maintainer runs the release-profile deploy command locally with Central credentials configured, a developer running `mvn -P release deploy` outside GitHub Actions activates this same release profile and automatically publishes the current checkout, without the workflow’s tag/version check; a local or untagged build can therefore consume a permanent Central version before the reviewed release.

Make automatic publishing opt-in via a property set only by the guarded release workflow, or otherwise enforce the workflow’s release checks for every invocation.

Comment thread pom.xml
<!-- 首次发版策略:false = 上传后停在 Portal 待发布,人工核对后手动 Publish -->
<autoPublish>false</autoPublish>
<!-- 链路上线策略:true = Portal 校验通过后自动发布(发布不可撤销,坐标永久公开) -->
<autoPublish>true</autoPublish>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟠 高 · 重新打标签会发布过时制品

当版本标签在原始发布任务仍在运行时被删除并重新指向另一个提交时,原始任务可能通过 autoPublish=true 发布其检出的提交,从而永久占用该版本号;之后,较新的运行会被拒绝,旧制品则继续公开。

当标签被重新指向时,取消正在进行的发布任务,并且只有在标签仍指向任务检出的提交时才允许上传。

另见 docs/release-guide.md:78-79。

提供给 AI 智能体的提示
在 `pom.xml` 第 222 行:

**重新打标签会发布过时制品**

当版本标签在原始发布任务仍在运行时被删除并重新指向另一个提交时,原始任务可能通过 `autoPublish=true` 发布其检出的提交,从而永久占用该版本号;之后,较新的运行会被拒绝,旧制品则继续公开。

当标签被重新指向时,取消正在进行的发布任务,并且只有在标签仍指向任务检出的提交时才允许上传。

另见 `docs/release-guide.md:78-79`。
Original comment in English

🟠 High · Retagged release publishes stale artifacts

When a version tag is deleted and repushed to a different commit while the original release job is still running, the original job can publish its checked-out commit through autoPublish=true, permanently occupying the version; the newer run is then rejected and the older artifacts remain public.

Cancel in-flight release jobs when a tag is retargeted and gate upload on the tag still pointing to the job’s checked-out commit.

Also at docs/release-guide.md:78-79.

Prompt for AI agents
In `pom.xml` at line 222:

**Retagged release publishes stale artifacts**

When a version tag is deleted and repushed to a different commit while the original release job is still running, the original job can publish its checked-out commit through `autoPublish=true`, permanently occupying the version; the newer run is then rejected and the older artifacts remain public.

Cancel in-flight release jobs when a tag is retargeted and gate upload on the tag still pointing to the job’s checked-out commit.

Also at `docs/release-guide.md:78-79`.

Comment thread docs/release-guide.md
Comment on lines +77 to +78
> **不可撤回提醒**:Central 发布后坐标永久公开、不可删除。上传前发现的任何问题,
> 直接丢弃(Discard)该部署,修完重新打 tag(删除 tag 重推即可,workflow 幂等)。

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 中 · 丢弃说明无法阻止发布

当操作人员在上传前发现版本存在问题并按照丢弃说明操作时,指南会要求他们丢弃一个尚不存在的部署;上传后,autoPublish=true 会在验证通过后立即发布,因此没有可用于阻止错误发布的丢弃时限。

请用新的指导替换“丢弃并重新打标签”的恢复说明,明确指出:上传前没有可供丢弃的部署,而自动发布后也不存在丢弃时限。

提供给 AI 智能体的提示
在 `docs/release-guide.md` 第 77-78 行:

**丢弃说明无法阻止发布**

当操作人员在上传前发现版本存在问题并按照丢弃说明操作时,指南会要求他们丢弃一个尚不存在的部署;上传后,`autoPublish=true` 会在验证通过后立即发布,因此没有可用于阻止错误发布的丢弃时限。

请用新的指导替换“丢弃并重新打标签”的恢复说明,明确指出:上传前没有可供丢弃的部署,而自动发布后也不存在丢弃时限。
Original comment in English

🟡 Medium · Discard guidance cannot stop release

When an operator finds a release issue before upload and follows the discard instruction, the guide directs operators to discard a deployment that does not yet exist; after upload, autoPublish=true publishes it as soon as validation passes, leaving no discard window to stop an erroneous release.

Replace the discard-and-retag recovery instruction with guidance that reflects there is no deployment to discard before upload and no discard window after automatic publication.

Prompt for AI agents
In `docs/release-guide.md` at lines 77-78:

**Discard guidance cannot stop release**

When an operator finds a release issue before upload and follows the discard instruction, the guide directs operators to discard a deployment that does not yet exist; after upload, `autoPublish=true` publishes it as soon as validation passes, leaving no discard window to stop an erroneous release.

Replace the discard-and-retag recovery instruction with guidance that reflects there is no deployment to discard before upload and no discard window after automatic publication.

| 测试/覆盖率 | 208 tests 全绿;聚合行/分支 100.00% |

**已按用户决策修正**:`autoPublish` true→false(首次发版人工核对后手动 Publish);release.yml 注释验证路径改为 DNS TXT(原注释写的 GitHub 仓库验证不适用于 com.wanlianyida)。
**已按用户决策修正**:`autoPublish` true→false(首次发版人工核对后手动 Publish);release.yml 注释验证路径改为 DNS TXT(原注释写的 GitHub 仓库验证不适用于 com.wanlianyida)。(0.3.0 起改回 `true`,见 CONTRIBUTING §8)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚪ 低 · 发布说明相互矛盾

当维护者查阅报告以了解当前发布流程时,docs/wop-sdk-report-java.md 声明发布需要手动点击 Publish,并提到 autoPublish=false;而发布指南则称 Portal 验证通过后会自动发布,因此读者会看到相互矛盾的说明。

更新报告中的发布策略描述及相关引用,使其与当前的自动发布流程一致。

另见 docs/release-guide.md:70。

提供给 AI 智能体的提示
在 `docs/wop-sdk-report-java.md` 第 219 行:

**发布说明相互矛盾**

当维护者查阅报告以了解当前发布流程时,`docs/wop-sdk-report-java.md` 声明发布需要手动点击 Publish,并提到 `autoPublish=false`;而发布指南则称 Portal 验证通过后会自动发布,因此读者会看到相互矛盾的说明。

更新报告中的发布策略描述及相关引用,使其与当前的自动发布流程一致。

另见 `docs/release-guide.md:70`。
Original comment in English

⚪ Low · Release instructions contradict each other

When a maintainer consults the report to understand the current release process, docs/wop-sdk-report-java.md says releases require manual Publish and refers to autoPublish=false, while the release guide says Portal validation publishes automatically, so readers get conflicting instructions.

Update the report’s release-policy description and reference to match the current automatic-publishing process.

Also at docs/release-guide.md:70.

Prompt for AI agents
In `docs/wop-sdk-report-java.md` at line 219:

**Release instructions contradict each other**

When a maintainer consults the report to understand the current release process, `docs/wop-sdk-report-java.md` says releases require manual Publish and refers to `autoPublish=false`, while the release guide says Portal validation publishes automatically, so readers get conflicting instructions.

Update the report’s release-policy description and reference to match the current automatic-publishing process.

Also at `docs/release-guide.md:70`.

@im47cn
im47cn merged commit 79b8521 into main Nov 17, 2026
22 checks passed
@im47cn
im47cn deleted the im47cn/snaggletooth branch November 17, 2026 11:35
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