Skip to content

[PR] release v0.1.211 - #5429

Closed
github-actions[bot] wants to merge 1 commit into
masterfrom
2026-11-01_release-v0.1.211-094019
Closed

github-actions[bot] wants to merge 1 commit into
masterfrom
2026-11-01_release-v0.1.211-094019

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Auto-fallback from the one-click release workflow: direct push to master was blocked by branch protection. Merging this PR publishes via the standard release.yml flow.

Changes since v0.1.210

@ranxianglei ranxianglei changed the title release v0.1.211 [PR] release v0.1.211 Nov 1, 2026
@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重:不重复,但存在同版本前序——PR #5419(第一次 v0.1.211 发布分支)已合入 master(merge commit aeda157),master 现在已含全部窗口内容与版本号 0.1.211;但 npm 上仍无 0.1.211(latest 仍是 0.1.210,v0.1.211 tag 也不存在)。本 PR 从 #5419 合并前的旧 master ref(c78ecb4,版本还是 0.1.210)切出 + 新 bump commit,合并后树与当前 master 完全等价——它的作用是触发 release.yml 完成发布。正在核查 #5419 那次合并没有触发发布的具体原因。

标签:pr + scope/ci + p3(例行发布流程,无缺陷内容)

开始 v0.1.210..HEAD 全窗回归审计(13 个非 merge 提交 / 29 文件,分批通读中),八问结论随后回复。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant