Skip to content

feat: backport the canary release channel rename (#4490) - #4493

Merged
Grapedge merged 1 commit into
release/2026-10-28from
backport/canary-channel-release-2026-10-28
Oct 28, 2026
Merged

Grapedge merged 1 commit into
release/2026-10-28from
backport/canary-channel-release-2026-10-28

Conversation

@Grapedge

Copy link
Copy Markdown
Collaborator

Requirement or Bug

把 #4490 回移到 release/2026-10-28,让这个分支发出的正式版不带 dev 渠道命名。

Bug Reproduction Steps

N/A

Root Cause

N/A

Code Changes

release/2026-10-28 @ ef3422209 (#4492)
  └─ cherry-pick 84a392e9c (#4490)

这是 #4490 的原样回移,不是新的改动。回移后,#4490 改动过的 23 个路径与 main 上的 84a392e9c 完全一致。

唯一的冲突在 scripts/dev-release.mjs 和 scripts/dev-release.test.mjs:#4490 删除了这两个文件,而 release 分支上的版本没有包含 #4469 的修复。以 main 上的版本为准,直接删除;替代它们的 scripts/canary-release.mjs 已经包含 #4469 的修复,#4469 不需要再单独回移。

不新增 changeset,理由同 #4490:dev 渠道没进过任何正式版本。这条回移合入后,这个分支发出的正式版也不会带上 dev 命名,因此不需要补 changeset。

合入这条 release 不会发版,发版仍要等 #4463 在这之后合入。

Behavior Changes and Affected Users

与 #4490 相同,见 #4490 的行为变化表。

release 分支上额外需要说明的一点:canary 发布 workflow 只允许从 main 发布(selectCanaryCommit 会拒绝其他 ref),所以 release 分支上的 workflow 和脚本改名不会触发任何发布;release 分支 CI 的 release-workflow-tests 改为运行 canary-release.test.mjs。

测试随 #4490 的提交一起回移。

Checklist

  • I have read the CONTRIBUTING document.
  • I have linked a related issue (external PRs: issue must have a maintainer's /approve).
  • I have added tests that prove my feature works.
  • The behavior-change table above is complete, and every removed behavior or flipped default is named in the changeset and either has an escape hatch or was explicitly approved by a maintainer in this PR.
  • Ran gen-changesets skill, or this PR needs no changeset.
  • Ran gen-docs skill, or this PR needs no doc update.

@changeset-bot

changeset-bot Bot commented Oct 28, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 491a6dc

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-28T10:29:53.463121Z 491a6dc PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@pkg-pr-new

pkg-pr-new Bot commented Oct 28, 2026

Copy link
Copy Markdown
pnpm dlx https://pkg.pr.new/@moonshot-ai/kimi-code@491a6dc
npx https://pkg.pr.new/@moonshot-ai/kimi-code@491a6dc

commit: 491a6dc

@Grapedge
Grapedge merged commit 039448b into release/2026-10-28 Oct 28, 2026
15 checks passed
@Grapedge
Grapedge deleted the backport/canary-channel-release-2026-10-28 branch October 28, 2026 10:32
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.

1 participant