The following items must be done before/during the V4 release to ensure a smooth transition.

• Changesets: Exit pre mode (changeset pre exit): https://changesets-docs.vercel.app/en/prereleases
• Vercel: Point domain: skeleton.dev to branch: main instead of branch: v3
• Vercel: Point domain: v3.skeleton.dev to branch: v3
• Vercel: Remove redirect from v3.skeleton.dev to skeleton.dev
• Docs: Revert @next tag in onboarding instructions (all frameworks)
• CLI: Change next tag to ^4.0.0 in transformPackageJson (and the tests for it)

Leading up the release we should:

• Do another pass through the contributor docs to detail said conventions while fresh in mind.
• I also need to write up new docs - including: the homepage, fundamentals, component examples
• Then around Wednesday I'll create the new RC announcement post and video to share with the community.
• Hugo: Audit for consistency, make sure we've adhered to our own conventions for all components top to bottom.
• Chris: do a style consistency pass for all components (comparing to v3 and Figma)
• Review any means to streamline the migration process for v2 and v3 users. Including a new migration guide.
• Update the framework repos to use Skeleton v4 (at or near release)
  • SvelteKit: https://github.com/skeletonlabs/skeleton-repl-sveltekit
  • Next.js: https://github.com/skeletonlabs/skeleton-repl-nextjs
  • Nuxt: https://github.com/skeletonlabs/skeleton-repl-nuxt
  • Solidstart: https://github.com/skeletonlabs/skeleton-repl-solidstart
  • Astro: https://github.com/skeletonlabs/skeleton-repl-astro
• Update GitHub Sponsors website templates (blog and portfolio)