Skip to content

Use new Status API from SB 9#359

Merged
JReinhold merged 41 commits intonextfrom
update-to-new-status-api
Mar 17, 2025
Merged

Use new Status API from SB 9#359
JReinhold merged 41 commits intonextfrom
update-to-new-status-api

Conversation

@JReinhold
Copy link
Copy Markdown
Contributor

@JReinhold JReinhold commented Mar 13, 2025

Updated to use the new status API

📦 Published PR as canary version: 3.2.7--canary.359.a5dfe67.0

✨ Test out this PR locally via:

npm install @chromatic-com/storybook@3.2.7--canary.359.a5dfe67.0
# or 
yarn add @chromatic-com/storybook@3.2.7--canary.359.a5dfe67.0

Version

Published prerelease version: v4.0.0-next.3

Changelog

💥 Breaking Change

🚀 Enhancement

🐛 Bug Fix

⚠️ Pushed to next

Authors: 3

@JReinhold JReinhold self-assigned this Mar 13, 2025
@ghengeveld ghengeveld changed the base branch from next to formatting March 14, 2025 14:18
Base automatically changed from formatting to next March 14, 2025 19:57
@JReinhold JReinhold changed the base branch from next to sb9-breaking-changes March 14, 2025 20:45
JReinhold added a commit to storybookjs/storybook that referenced this pull request Mar 14, 2025
"typeId": "chromaui/addon-visual-tests",
"value": "status-value:success",
},
]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a deviation from our current behavior, but I think it's an improvement.

expect(args.updateBuildStatus).toHaveBeenCalledWith([]);
});
},
} satisfies Story;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's purpose is to visualize the "empty" state of a branch, where no builds have been run against it yet.

Screenshot 2025-03-17 at 13 22 57

The custom render function is just a hack to work around the fact that updateBuildStatus used to accept a callback function besides a value.

@JReinhold JReinhold force-pushed the sb9-breaking-changes branch from 9d442d5 to e9a2346 Compare March 17, 2025 12:31
Base automatically changed from sb9-breaking-changes to next March 17, 2025 13:08
@JReinhold JReinhold merged commit 6bad2bd into next Mar 17, 2025
2 of 4 checks passed
@JReinhold JReinhold deleted the update-to-new-status-api branch March 17, 2025 13:08
@ghengeveld
Copy link
Copy Markdown
Member

@JReinhold shouldn't this be labeled major considering it's a breaking change due to the requirement for SB 9? The label is relevant to changelog generation.

@ghengeveld
Copy link
Copy Markdown
Member

🚀 PR was released in v4.0.0 🚀

@ghengeveld ghengeveld added released Verdict: This issue/pull request has been released and removed prerelease labels May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Classification: Improvement to existing feature patch Auto: Increment the patch version when merged release Auto: Create a `latest` release when merged released Verdict: This issue/pull request has been released

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants