Skip to content

Release: Preminor alpha 9.2.0-alpha.0#32165

Merged
yannbf merged 1 commit into
next-releasefrom
version-non-patch-from-9.1.0
Jul 31, 2025
Merged

Release: Preminor alpha 9.2.0-alpha.0#32165
yannbf merged 1 commit into
next-releasefrom
version-non-patch-from-9.1.0

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 31, 2025

Copy link
Copy Markdown
Contributor

This is an automated pull request that bumps the version from 9.1.0 to 9.2.0-alpha.0.
Once this pull request is merged, it will trigger a new release of version 9.2.0-alpha.0.
If you're not a core maintainer with permissions to release you can ignore this pull request.

To do

Before merging the PR, there are a few QA steps to go through:

  • Add the "freeze" label to this PR, to ensure it doesn't get automatically forced pushed by new changes.
  • Add the "ci:daily" label to this PR, to trigger the full test suite to run on this PR.

And for each change below:

  1. Ensure the change is appropriate for the version bump. E.g. patch release should only contain patches, not new or de-stabilizing features. If a change is not appropriate, revert the PR.
  2. Ensure the PR is labeled correctly with one of: "BREAKING CHANGE", "feature request", "bug", "maintenance", "dependencies", "documentation", "build", "unknown".
  3. Ensure the PR title is correct, and follows the format "[Area]: [Summary]", e.g. "React: Fix hooks in CSF3 render functions". If it is not correct, change the title in the PR.
    • Areas include: React, Vue, Core, Docs, Controls, etc.
    • First word of summary indicates the type: “Add”, “Fix”, “Upgrade”, etc.
    • The entire title should fit on a line

This is a list of all the PRs merged and commits pushed directly to next, that will be part of this release:

If you've made any changes doing the above QA (change PR titles, revert PRs), manually trigger a re-generation of this PR with this workflow and wait for it to finish. It will wipe your progress in this to do, which is expected.

Feel free to manually commit any changes necessary to this branch after you've done the last re-generation, following the Make Manual Changes section in the docs, especially if you're making changes to the changelog.

When everything above is done:


Generated changelog

9.2.0-alpha.0

Greptile Summary

This PR is an automated preminor alpha release that bumps Storybook's version from 9.1.0 to 9.2.0-alpha.0. This represents the beginning of a new minor version development cycle (9.2.x). The changes are minimal and focused on version infrastructure updates:

  1. Version tracking update: Adds a deferredNextVersion field to the root package.json with the value "9.2.0-alpha.0". This field is used by Storybook's release tooling to coordinate version management across their monorepo structure.

  2. Changelog preparation: Creates a new empty entry in CHANGELOG.prerelease.md for version 9.2.0-alpha.0. The empty content is expected for an initial alpha release - changes will be populated as development progresses.

  3. Documentation version update: Updates docs/versions/next.json to reflect the new version with an empty info field, which will be populated as release notes are finalized.

This follows Storybook's established automated release process where alpha versions serve as preparation for the next development cycle. The empty changelog and info fields indicate this is purely infrastructure setup rather than a release with actual feature changes.

Confidence score: 5/5

  • This PR is extremely safe to merge as it only contains automated version infrastructure updates with no functional code changes.
  • The changes follow Storybook's well-established release process patterns and are consistent with previous version bumps seen in the changelog history.
  • All files need minimal attention as they contain standard automated version management updates.

@github-actions github-actions Bot requested a review from kylegach as a code owner July 31, 2025 16:18
@github-actions github-actions Bot added the release For PRs that trigger new releases. Automated label Jul 31, 2025
@github-actions github-actions Bot requested a review from jonniebigodes as a code owner July 31, 2025 16:18

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

3 files reviewed, no comments

Edit Code Review Bot Settings | Greptile

@yannbf yannbf added the freeze Freeze the Release PR with this label label Jul 31, 2025
@yannbf yannbf merged commit b60704c into next-release Jul 31, 2025
@yannbf yannbf deleted the version-non-patch-from-9.1.0 branch July 31, 2025 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

freeze Freeze the Release PR with this label release For PRs that trigger new releases. Automated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants