Skip to content

Release: Prerelease 10.2.0-alpha.19#33551

Closed
github-actions[bot] wants to merge 6 commits into
next-releasefrom
version-non-patch-from-10.2.0-alpha.18
Closed

Release: Prerelease 10.2.0-alpha.19#33551
github-actions[bot] wants to merge 6 commits into
next-releasefrom
version-non-patch-from-10.2.0-alpha.18

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This is an automated pull request that bumps the version from 10.2.0-alpha.18 to 10.2.0-alpha.19.
Once this pull request is merged, it will trigger a new release of version 10.2.0-alpha.19.
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: CSF-Factories: Allow kebab-case HTML attribute names in web components args #33526
  • 🐛 Bug: CSF-Factories: Export WebComponentsTypes and VueTypes #33521
  • 🐛 Bug: CLIInitiate: Simplify the CLI init port flag detection #33546
  • 🐛 Bug: Initiate: Fix used port flag handling #33544
  • 📦 Dependencies: NextJSVite: Upgrade plugin #33538
  • 🐛 Bug: Manager: Fix system query parameters being overridable #33535
  • 🏗️ Build: CircleCI: Dynamic config setup #32925
  • 🏗️ Build: E2E: Fix MCP tests also running in Preact sandboxes #33545
  • 🏗️ Build: Manifests and MCP: Add e2e tests #33514

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.2.0-alpha.19

  • CLIInitiate: Simplify the CLI init port flag detection - #33546, thanks ndelangen!
  • CSF-Factories: Allow kebab-case HTML attribute names in web components args - #33526, thanks kasperpeulen!
  • CSF-Factories: Export WebComponentsTypes and VueTypes - #33521, thanks kasperpeulen!
  • Initiate: Fix used port flag handling - #33544, thanks ndelangen!
  • Manager: Fix system query parameters being overridable - #33535, thanks JReinhold!
  • NextJSVite: Upgrade plugin - #33538, thanks ndelangen!

kasperpeulen and others added 6 commits January 13, 2026 10:11
When using CSF factories with `meta.story()`, the return type references
`WebComponentsTypes` and `VueTypes` constraints, but these types were not
exported from the package's public API, causing TS4023 errors:

"Exported variable 'Default' has or is using name 'WebComponentsTypes'"

This follows the existing pattern from @storybook/react which already
exports `ReactTypes`.

Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
…s args

When using @wc-toolkit/storybook-helpers or similar libraries that generate
args with kebab-case attribute names (e.g., 'static-color'), TypeScript
would error because our types only allowed camelCase property names.

This adds `InferArgsFromComponent<C>` which allows both:
- camelCase properties from HTMLElementTagNameMap (type-checked)
- kebab-case strings containing `-` (for HTML attributes)

Since JavaScript property names cannot contain `-`, any string with a dash
is definitively an HTML attribute name, making this a safe heuristic.

Closes #33524

Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
…port

CSF-Factories: Export WebComponentsTypes and VueTypes
…kebab-case-args

CSF-Factories: Allow kebab-case HTML attribute names in web components args
@github-actions github-actions Bot added the release For PRs that trigger new releases. Automated label Jan 15, 2026
@ndelangen ndelangen closed this Jan 15, 2026
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.

3 participants