[Bug]: Missing minimumReleaseAge prompt when initializing Storybook with pnpm 12
Author: ia319Created Sep 17, 2026Updated Sep 17, 2026
Labelsbugneeds triage
Describe the bug
When the Storybook CLI is already cached from another project, pnpm create storybook starts in a project with minimumReleaseAge configured, but does not show the prompt to exclude Storybook packages or use an older release.
It generates configuration files and updates package.json, then dependency installation fails because of the waiting period, leaving the project partially initialized.
Reproduction link
https://github.com/vitejs/vite/tree/main/packages/create-vite/template-react-ts
Reproduction steps
- Use pnpm 12.4.2.
- In project A, without a custom minimum release age, run:
This downloads and caches the CLI.pnpm create [email protected] - In project B, an existing React + Vite project, configure
minimumReleaseAgeto exceed the age of Storybook 10.6.0. Do not add Storybook exclusions. - Using the same environment while the CLI cache is still valid, run:
pnpm create [email protected] - Complete the initialization prompts. No minimum-release-age prompt appears, and dependency installation fails.
Expected: show the waiting-period prompt before generating files or updating dependencies.
System
npm: 12.0.0 - /home/.nvm/versions/node/v24.15.0/bin/npm
pnpm: 12.4.2 - /home/.nvm/versions/node/v24.15.0/bin/pnpm
Additional context
Without the cached CLI, pnpm may block its download before Storybook starts.
This report concerns initialization after the cached CLI successfully starts.
Source: storybookjs/storybook