Skip to content

Force Storybook build publish - #3051

Closed
rajsite wants to merge 2 commits into
mainfrom
sb-force-rebuild
Closed

Force Storybook build publish#3051
rajsite wants to merge 2 commits into
mainfrom
sb-force-rebuild

Conversation

@rajsite

@rajsite rajsite commented Aug 30, 2026

Copy link
Copy Markdown
Member

Pull Request

🤨 Rationale

It was found that storybook had a behavior change where if turbosnap is enabled and no turbosnap changes are found then chromatic skipped publishing the new storybook build altogether, see example log that only had changes to example apps:

13:50:14.325 Chromatic CLI v18.7.1
             https://www.chromatic.com/docs/cli
13:50:14.326 Authenticating with Chromatic
13:50:14.326     → Connecting to https://index.chromatic.com/
13:50:14.492 Authenticated with Chromatic
13:50:14.492     → Using project token '********e1a6'
13:50:14.493 Retrieving git information
13:50:16.315 Found 22 changed files:
               change/@ni-ok-angular-9f7c8d31-1d92-4ea1-9b20-6f4b5a8d0c63.json
               change/@ni-ok-components-2f07bb8e-4e7b-4f0f-9b4f-5c9ddf7d7e44.json
               change/@ni-ok-react-f1b3a2c4-6d7e-48f0-9a1b-2c3d4e5f6071.json
               package-lock.json
               packages/angular-workspace/example-client-app/src/app/customapp/anchor-tabs-section.component.ts
               packages/angular-workspace/example-client-app/src/app/customapp/tabs-section.component.ts
               packages/angular-workspace/ok-angular/CHANGELOG.json
               packages/angular-workspace/ok-angular/CHANGELOG.md
               packages/angular-workspace/ok-angular/package.json
               packages/blazor-workspace/Examples/Demo.Shared/Pages/Sections/AnchorTabsSection.razor
               packages/blazor-workspace/Examples/Demo.Shared/Pages/Sections/TabsSection.razor
               packages/blazor-workspace/OkBlazor/CHANGELOG.json
               packages/blazor-workspace/OkBlazor/CHANGELOG.md
               packages/blazor-workspace/OkBlazor/package.json
               packages/ok-components/CHANGELOG.json
               packages/ok-components/CHANGELOG.md
               packages/ok-components/package.json
               packages/react-workspace/ok-react/CHANGELOG.json
               packages/react-workspace/ok-react/CHANGELOG.md
               packages/react-workspace/ok-react/package.json
               packages/react-workspace/react-client-app/src/components/AnchorTabsSection.tsx
               packages/react-workspace/react-client-app/src/components/TabsSection.tsx
13:50:16.318 Retrieved git information
13:50:16.319     → Commit '64d9738' on branch 'selects-example-apps'; found 1 parent build and 22 changed files
13:50:16.319 Collecting Storybook metadata
13:50:16.374 No viewlayer package listed in dependencies. Checking transitive dependencies.
13:50:16.377 Collected Storybook metadata
13:50:16.378     → Build metadata gathered
13:50:16.378 Initializing build
13:50:17.590 Initialized build
13:50:17.590     → Build 14673 initialized
13:50:17.590 Building your Storybook
13:50:17.591 Build Storybook [skipped]
13:50:17.591     → Using prebuilt Storybook at ./packages/site/dist/storybook
13:50:17.592 Prepare your built Storybook
13:50:17.592     → Validating Storybook files
13:50:17.605     → Traversing dependencies for 22 files that changed since the last build
13:50:20.415 Found 6 changed dependencies:
               @ni/ok-components
               @ni/ok-react
               @ni-private/storybook
               @ni-private/react-client-app
               @ni-private/blazor-workspace
               @ni-private/angular-workspace
13:50:20.477 Found affected story files:
             
13:50:20.478     → Found 0 story files affected by recent changes
13:50:20.478     → Calculating file hashes
13:50:20.566 Preparation complete
13:50:20.567     → Storybook files validated and prepared for upload
13:50:20.567 Publishing your built Storybook
13:50:20.567     → Starting publish
13:50:21.923 ✔ TurboSnap enabled
             Bypassed 1101 snapshots because no frontend files were changed.
13:50:21.924 ✔ This build was skipped and will not be displayed in Chromatic.
             The passed status will be carried over from the most recent ancestor build.
             ℹ View ancestor build details at https://www.chromatic.com/build?appId=60e89457a987cf003efc0a5b&number=14655
             
13:50:21.924 Publishing your built Storybook

See PR discussion where behavior was noted and see discussion that first attempted to address the behavior.

👩‍💻 Implementation

  • Enable the forceRebuild flag
  • Made a minor example app alignment change to exercise workflow

🧪 Testing

  • Pushed one commit that was example app only changes
  • Pushed a commit that enabled force rebuild and verified turbosnaps still utilized

✅ Checklist

  • I have updated the project documentation to reflect my changes or determined no changes are needed.

@rajsite rajsite changed the title Force storybook rebuild Force Storybook build publish Aug 30, 2026
@rajsite

rajsite commented Aug 30, 2026

Copy link
Copy Markdown
Member Author

Aww dang, doesn't look like forceRebuild worked :(
Edit reason: forceRebuild and onlyChanged are documented as incompatible options.

@rajsite

rajsite commented Aug 30, 2026

Copy link
Copy Markdown
Member Author

Created a sb issue: chromaui/chromatic-cli#1472

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant