[Stage 1.6] Migrate and validate the v2 release workflow for the monorepo
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 38/100
- Issue 类型
- 重构
- 描述清晰度
- 描述清楚
- 活跃度
- 冷清
- 技术栈
- javascript, playwright, react, typescript
- 领域
- build-system, ci-cd, devops, release
调研方向
Start with release-v2.yml and the Stage 1 pnpm workspace/package build configuration, then trace public-package selection, versioning, approval, and npm publishing. Review the release-related tests and consumer fixtures, especially the vanilla JavaScript, React, and Playwright entry points. Done means a v2 prerelease is published only under next after approval, all versions and artifacts agree, private packages cannot leak into published dependencies, and the stable cutover is covered by a dry-run.
由索引模型根据 Issue 内容生成。
描述
Parent: #318
Goal
Prove that v2 can be released and consumed from npm after the repository becomes a pnpm monorepo.
The workflow is a production delivery path, not only a build check.
Scope
- Keep
release-v2.ymltriggered by thev2branch before cutover. - Replace root-package npm assumptions with the Stage 1 pnpm workspace and package build model.
- Build and publish only public packages.
- Prevent private workspace packages from being published.
- Prevent unresolved imports or published dependencies on private packages.
- Permit only
2.xprereleases fromv2. - Publish under
next; never updatelatestbefore cutover. - Keep release creation behind a reviewed release pull request or equivalent approval.
- Verify generated versions, changelogs, Git tags, GitHub Releases, package manifests, and npm artifacts.
- Install the published prerelease from npm in clean vanilla JavaScript, React, and applicable Playwright consumer fixtures.
- Document the cutover-only configuration change from
v2/nexttomain/latest. - Provide a dry-run for the future stable v2 release path.
Acceptance criteria
-
release-v2.ymlruns fromv2using pnpm and the monorepo package graph. - Only intended public packages are publishable.
- A
2.xprerelease is published undernextafter explicit approval. - The prerelease does not update
latest. - Version, changelog, tag, GitHub Release, manifest, and npm artifact agree.
- Published packages contain no unresolved private-package imports or dependencies.
- Clean consumer fixtures install from npm without workspace access.
- Root, React, and applicable Playwright entry points pass runtime and type checks.
- The
main/latestcutover configuration is covered by a safe dry-run.
- 主要语言
- TypeScript
- 星标
- 145
- 派生
- 12
- 平均合并
- 1 天 14 小时
- 30 天内合并 PR
- 43
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
gravity-ui/graph 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
gravity-ui/graph#457 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
gravity-ui/graph#455 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 55/100
gravity-ui/graph#456 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
gravity-ui/graph#431 ·
维护者通常 1 天内回复
-
proposal
难度 5/5 一周以上 新手友好度 25/100
gravity-ui/graph#416 ·
维护者通常 1 天内回复
相似的 Issue
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
难度 2/5 1-3 小时 新手友好度 68/100
openclaw/openclaw#199885 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
-
feature needs-triage
难度 2/5 1-3 小时 新手友好度 78/100
BoardGamesEmpire/board-games-empire-backend#1306 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 80/100
sequant-io/sequant#1689 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 80/100