Skip to content

chore: release packages (next) - #4092

Open
github-actions[bot] wants to merge 1 commit into
v6from
changeset-release/v6
Open

github-actions[bot] wants to merge 1 commit into
v6from
changeset-release/v6

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to v6, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

v6 is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on v6.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

The changelog information of each package has been omitted from this message, as the content exceeds the size limit.

@ark-ui/codemod@6.0.0-next.0

@ark-ui/react@6.0.0-next.0

@ark-ui/solid@6.0.0-next.0

@ark-ui/svelte@6.0.0-next.0

@ark-ui/vue@6.0.0-next.0

@vercel

vercel Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
ark-docs Ready Ready Preview Sep 23, 2026 3:58pm UTC

Request Review

@aaron-easygo

Copy link
Copy Markdown
Contributor

Question on sequencing rather than this PR's contents: is main merged forward into v6 before 6.0.0 exits pre mode?

v6 is currently 125 ahead / 20 behind main, and three things that landed on the v5 line are not on it — #4055 (the Svelte Fieldset namespace still exports flat FieldsetRootProps), #4071 (check:nodes is still the dialog-only version that cannot see the Svelte adapter) and #4084 (the seven Svelte parts realigned to the element the other adapters render). If the answer is "yes, main merges forward", nothing needs doing and I'll stop worrying about it. If v6 rewrote those files enough that a merge won't carry them, I'm happy to re-port any of the three against v6 — say the word and I'll open them.

Asking because #4071's list is shrink-only by design: re-landing it on v6 after the elements have already diverged again is more work than carrying it across now.

@Adebesin-Cell

Copy link
Copy Markdown
Collaborator

Question on sequencing rather than this PR's contents: is main merged forward into v6 before 6.0.0 exits pre mode?

v6 is currently 125 ahead / 20 behind main, and three things that landed on the v5 line are not on it — #4055 (the Svelte Fieldset namespace still exports flat FieldsetRootProps), #4071 (check:nodes is still the dialog-only version that cannot see the Svelte adapter) and #4084 (the seven Svelte parts realigned to the element the other adapters render). If the answer is "yes, main merges forward", nothing needs doing and I'll stop worrying about it. If v6 rewrote those files enough that a merge won't carry them, I'm happy to re-port any of the three against v6 — say the word and I'll open them.

Asking because #4071's list is shrink-only by design: re-landing it on v6 after the elements have already diverged again is more work than carrying it across now.

Hey @aaron-easygo, v6 is on its own line, so those changes aren't part of this. This PR is just prep to kick off the beta of Ark v6. We'd bring the v5 improvements over to the v6 branch and maybe ship them with the first beta. But I wanted to ask: are you interested in trying out the beta?

@aaron-easygo

Copy link
Copy Markdown
Contributor

@Adebesin-Cell ahh thanks for the info mate. I'd be interested in testing it out, but we're currently building out a DS where stability is a main concern, so the v5 branch is where our efforts are focused atm. If you want to send me details on testing v6 I'll find some time to report bugs

@github-actions
github-actions Bot force-pushed the changeset-release/v6 branch from e6701a6 to 17148b1 Compare September 23, 2026 08:20
@Adebesin-Cell

Copy link
Copy Markdown
Collaborator

@Adebesin-Cell ahh thanks for the info mate. I'd be interested in testing it out, but we're currently building out a DS where stability is a main concern, so the v5 branch is where our efforts are focused atm. If you want to send me details on testing v6, I'll find some time to report bugs

No worries. Yep! Good call. When v6 is ready for stable release, we'll announce it. We also made codemods for different changes and documented some that need extra care.

Oh, thanks! I'll send the details for testing shortly.

Also, I managed to port over #4097 some of the v5 changes you mentioned. I'll be working on the rest this week.

@Adebesin-Cell

Copy link
Copy Markdown
Collaborator

Here are the testing details @aaron-easygo, after this PR gets merged, it'll release a new tag under version 6.

Then you can install it using.

npm i @ark-ui/react@next   # or @ark-ui/solid / @ark-ui/svelte / @ark-ui/vue

Start here: V6 migration guide — install, what changed, and the codemods. Most of the migration is npx @ark-ui/codemod list.

Feedback goes in the v6 discussion. Most useful: anything the codemod gets wrong or misses, a breaking change that wasn't clear, or build/type errors after upgrading, with a small repro.

This branch was successfully deployed

1 active deployment
Preview — fdb82a18 Deployed Sep 23, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants