Skip to content

docs(skill): fold v0.2.9 release learnings into the release-manager skill - #2429

Open
fengmk2 wants to merge 1 commit into
mainfrom
docs/release-manager-v029-learnings
Open

docs(skill): fold v0.2.9 release learnings into the release-manager skill#2429
fengmk2 wants to merge 1 commit into
mainfrom
docs/release-manager-v029-learnings

Conversation

@fengmk2

@fengmk2 fengmk2 commented Aug 12, 2026

Copy link
Copy Markdown
Member

Step 9 of the release-manager skill, from running the full ecosystem-ci catalog for v0.2.9. Written generically, with no versions or project names.

  • Registry-bridge fetch flakes get their own triage bucket, placed first. Platform bindings are optionalDependencies, so a dropped tarball fetch leaves a "successful" install that dies later with Cannot find native binding. That reads like an unpublished package; it is not. Adds the packument check and the re-run command.
  • Weight forks by their actual prior pin, read from the upgrade commit rather than HEAD. A fork several releases behind tests a multi-release jump, not the release under review.
  • Run the isolated-home control from inside the project directory, or vp delegates to the checkout's packages/cli/dist and the comparison is void.
  • vp upgrade reports a false pass when a control home is still on PATH or exported via VP_HOME. Adds a clean-environment check.
  • Kill the whole process tree on driver timeout: an orphaned pnpm install holds the store lock and the next project looks hung.
  • Two fork-CI blockers are worth fixing rather than reporting, both test-branch only: no pull_request trigger, and third-party runner labels.

Catalog-side counterpart: vite-plus-ecosystem-ci/.github#3.

Draft for review.

@netlify

netlify Bot commented Aug 12, 2026

Copy link
Copy Markdown

Deploy Preview for viteplus-preview canceled.

Name Link
🔨 Latest commit 34ea891
🔍 Latest deploy log https://app.netlify.com/projects/viteplus-preview/deploys/6a7edddf259aa400089f50a1

…kill

Four things that generalize, from running the full ecosystem catalog:

- Registry-bridge tarball flakes are the most common false alarm, and
  the platform-binding case is actively misleading: because the binding
  is an optionalDependency, a dropped fetch leaves a 'successful'
  install that dies later with 'Cannot find native binding'. That reads
  like an unpublished package. Check the packument and re-run first.
- Weight the forks that were actually on the previous release. A fork
  several releases behind tests a multi-release jump, not the release
  under review, and its pin must be read from the upgrade commit rather
  than HEAD.
- Run the isolated-home control from inside the project directory, or
  vp delegates to the vite-plus checkout's dist and the comparison is
  silently invalid.
- vp upgrade reports success against a leaked VP_HOME or a control home
  left on PATH, so verify in a clean environment.

Also: kill the whole process tree when a parallel driver times out (an
orphaned pnpm holds the store lock and the next project looks hung),
and fix rather than report the two fork-CI blockers (no pull_request
trigger, third-party runner labels).
@fengmk2
fengmk2 force-pushed the docs/release-manager-v029-learnings branch from 1742036 to 34ea891 Compare August 14, 2026 09:20
@fengmk2
fengmk2 requested a review from wan9chi August 14, 2026 09:37
@fengmk2 fengmk2 self-assigned this Aug 14, 2026
@fengmk2
fengmk2 marked this pull request as ready for review August 14, 2026 09:38
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