[Stage 1.6] Migrate and validate the v2 release workflow for the monorepo
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 38/100
- Tipo de issue
- Refactorización
- Claridad
- Bien especificado
- Estado de actividad
- Tranquilo
- Stack tecnológico
- javascript, playwright, react, typescript
- Área
- build-system, ci-cd, devops, release
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 145
- Forks
- 12
- Merge medio
- 1 d 14 h
- PR fusionados (30 d)
- 43
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de gravity-ui/graph
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
gravity-ui/graph#457 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
gravity-ui/graph#455 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
gravity-ui/graph#456 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
gravity-ui/graph#431 ·
Los mantenedores suelen responder en 1 día
-
proposal
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
gravity-ui/graph#416 ·
Los mantenedores suelen responder en 1 día
Todos los issues de gravity-ui/graph
Issues similares
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
openclaw/openclaw#199885 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
feature needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
BoardGamesEmpire/board-games-empire-backend#1306 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
sequant-io/sequant#1689 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100