Skip to content

Conversation

@al1maher
Copy link
Contributor

Updated the migration page by adding some of the changes that I noticed and are not documented

  • 📖 Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

  • Documented the removal of prevent-close and the new dismissible prop for UModal and USlideover.
  • Added notes about the v-model change in UPagination (v-model:page instead of v-model).
  • Updated documentation for USelect, USelectMenu, and URadioGroup regarding the new change event behavior and the shift to using update:model-value for receiving the selected value.

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@github-actions github-actions bot added the v3 #1289 label Dec 11, 2025
@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 11, 2025

npm i https://pkg.pr.new/@nuxt/ui@5655

commit: d6fc356

@benjamincanac
Copy link
Member

This PR targets v3 branch to update https://ui3.nuxt.com/, is this intended? We might need to backport those changes to v3` migration guide on v4 branch as well: https://github.com/nuxt/ui/blob/v4/docs/content/docs/1.getting-started/3.migration/2.v3.md

@al1maher
Copy link
Contributor Author

al1maher commented Dec 12, 2025

This PR targets v3 branch to update https://ui3.nuxt.com/, is this intended? We might need to backport those changes to v3` migration guide on v4 branch as well: https://github.com/nuxt/ui/blob/v4/docs/content/docs/1.getting-started/3.migration/2.v3.md

I'm not sure I'm following you well, but in my work, we migrated v2 to v3. We yet to migrate to v4.

I just noticed that the migration guide is yet to be fully completed so I decided to add some of the breaking changes I noticed.

Copy link
Member

What I meant is the migration guide on ui3.nuxt.com https://ui3.nuxt.com/getting-started/migration also exists on ui.nuxt.com: https://ui.nuxt.com/docs/getting-started/migration/v3

@al1maher
Copy link
Contributor Author

What I meant is the migration guide on ui3.nuxt.com https://ui3.nuxt.com/getting-started/migration also exists on ui.nuxt.com: https://ui.nuxt.com/docs/getting-started/migration/v3

So should I apply the same changes on v4 and open a new PR or how should this "backport" work?

@benjamincanac benjamincanac merged commit f6d0ba1 into nuxt:v3 Dec 16, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v3 #1289

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants