[Cutover] Create the v1 maintenance line and promote v2 to main

未关闭
#332 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
github-actions, typescript
领域
release

调研方向

Start by checking the release workflows release-v2.yml and release-v1.yml, then review the related cutover work in #311 and confirm the listed preconditions and owners. Follow the four execution stages in the issue, verifying each exit criterion before proceeding. Done means v2 is promoted through a reviewed pull request, both release channels and branches are validated, npm artifacts and rollback procedures are verified, and the observation window passes.

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

描述

Goal

Promote the proven v2 release line to main while preserving the final v1 state as an independently maintainable release/v1 line.

Preconditions

  • All required v2 stages are complete.
  • release-v2.yml has published and consumer-verified an approved release candidate from v2 under next.
  • There is no unresolved relevant drift from main.
  • The cutover owner, release window, rollback owner, and go/no-go criteria are approved.
  • Old or conflicting release pull requests are completed or closed.
  • Rulesets targeting the future release/v1 branch are active before branch creation.
  • The cutover changes for both release workflows are prepared on v2.

Exit criteria

  • The final stable 1.x release is published from main and its exact commit is recorded.
  • release/v1 is created from that exact commit and is protected immediately.
  • A v1 release dry-run from release/v1 succeeds.
  • The final main state is synchronized into v2 with a merge commit.
  • The final v2 release candidate is revalidated under next.
  • v2 is promoted to main through a reviewed pull request without rewriting history.
  • Post-merge CI passes before a stable v2 release is approved.
  • release-v2.yml targets main, permits stable 2.x, and owns latest.
  • release-v1.yml targets release/v1, permits only 1.x, and uses v1.
  • Published v2 artifacts are installed and verified from npm.
  • Rollback procedures before and after npm publication are documented.
  • The observation window completes without a release-blocking regression.

Execution order

  1. Freeze v1, prepare protection, and create release/v1.
  2. Perform the final manual sync and approve the final v2 release candidate.
  3. Promote v2 to main and switch the stable release channels.
  4. Complete the observation window.

The first real v1 maintenance release is tracked separately in #311 and does not block cutover completion.

主要语言
TypeScript
星标
145
派生
12
平均合并
1 天 14 小时
30 天内合并 PR
43

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

gravity-ui/graph 的其他 Issue

查看 gravity-ui/graph 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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