[Stage 1.6] Migrate and validate the v2 release workflow for the monorepo

Abierto
#333 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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

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.yml triggered by the v2 branch 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.x prereleases from v2.
  • Publish under next; never update latest before 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/next to main/latest.
  • Provide a dry-run for the future stable v2 release path.

Acceptance criteria

  • release-v2.yml runs from v2 using pnpm and the monorepo package graph.
  • Only intended public packages are publishable.
  • A 2.x prerelease is published under next after 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/latest cutover 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

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de gravity-ui/graph

Todos los issues de gravity-ui/graph

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.