Skip to content

fix(release): accept both Memmy release branch formats - #286

Open
MLittleprince wants to merge 1 commit into
MemTensor:mainfrom
MLittleprince:codex/release-branch-compat-v2
Open

fix(release): accept both Memmy release branch formats#286
MLittleprince wants to merge 1 commit into
MemTensor:mainfrom
MLittleprince:codex/release-branch-compat-v2

Conversation

@MLittleprince

Copy link
Copy Markdown
Collaborator

目标

GitHub Draft Release v2 同时兼容团队实际使用的两种发版分支:

  • vX.Y.Z
  • release/vX.Y.Z

解决 v1.1.0 这类分支合入 main 后工作流被 Skipped、无法自动创建 Draft Release 的问题。

安全边界

  • 仍只接受合入 main 的已合并 PR
  • 仍只接受主仓分支,不接受 fork PR 自动发版
  • 仍要求严格、无前后缀的 SemVer 分支名
  • 保留仓库级串行锁,避免重复创建 tag / Draft Release
  • 后续仍执行完整版本、安装包、checksum、evidence 和 106 配置预检
  • 只创建 Draft Release,不自动 Publish、不直接修改官网或发布 production

验证

  • npm run test:release-workflow:20/20 通过
  • 合法分支 v1.1.0release/v1.1.0 均可解析版本
  • 非法分支 version-fixv1.1v1.1.0-betafork/v1.1.0 均被拒绝
  • git diff --check:通过
  • Workflow YAML 语法检查:通过

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