Skip to content

Release: Prerelease 10.4.0-alpha.5#34322

Open
github-actions[bot] wants to merge 10 commits intonext-releasefrom
version-non-patch-from-10.4.0-alpha.4
Open

Release: Prerelease 10.4.0-alpha.5#34322
github-actions[bot] wants to merge 10 commits intonext-releasefrom
version-non-patch-from-10.4.0-alpha.4

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 25, 2026

This is an automated pull request that bumps the version from 10.4.0-alpha.4 to 10.4.0-alpha.5.
Once this pull request is merged, it will trigger a new release of version 10.4.0-alpha.5.
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:

  • 🐛 Bug: Builder-Vite: Use djb2 hash to prevent variable name collisions in builder-vite #34274 (will also be patched)
  • ✨ Feature Request: Core: Add changeDetection feature flag #34314

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

10.4.0-alpha.5

  • Builder-Vite: Use djb2 hash to prevent variable name collisions in builder-vite - #34274, thanks chida09!
  • Core: Add changeDetection feature flag - #34314, thanks valentinpalkovic!

chida09 and others added 8 commits March 23, 2026 22:20
…ns with pnpm

Replace the naive character-code-sum hash with djb2 to prevent collisions
when pnpm peer dependency hash suffixes produce paths with identical sums.

Closes #34270

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Move the unsigned right shift inside the loop so the accumulator stays
within 32-bit range on every iteration, avoiding precision loss when
hashing long file paths (common with pnpm).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…flag

Core: Add changeDetection feature flag
@github-actions github-actions bot added the release For PRs that trigger new releases. Automated label Mar 25, 2026
valentinpalkovic and others added 2 commits March 25, 2026 19:25
…llision

Builder-Vite: Use djb2 hash to prevent variable name collisions in builder-vite
@storybook-bot storybook-bot force-pushed the version-non-patch-from-10.4.0-alpha.4 branch from 2bf29a5 to ce8a0a0 Compare March 25, 2026 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release For PRs that trigger new releases. Automated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants