Skip to content

Version Packages#1289

Merged
benmccann merged 1 commit intomainfrom
changeset-release/main
Feb 23, 2026
Merged

Version Packages#1289
benmccann merged 1 commit intomainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Feb 23, 2026

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 main, this PR will be updated.

Releases

@sveltejs/vite-plugin-svelte@7.0.0

Major Changes

  • breaking(deps): require vite 8 (#1266)

  • breaking(options): remove deprecated options (#1274)

    • vitePlugin.hot in svelte.config.js
      use compilerOptions.hmr instead
    • vitePlugin.ignorePluginPreprocessors in svelte.config.js
      no longer needed
    • api.idFilter of vite-plugin-svelte:api
      use api.filter instead
    • plugin.api.sveltePreprocess of other vite plugins
      Update affected plugins to a newer version or remove them.
      See docs for more information.
  • breaking(dev): no longer overrides compilerOptions.cssHash because Svelte now produces a stable css hash by itself (#1271)

  • breaking(inspector): integrate vite-plugin-svelte-inspector into vite-plugin-svelte to avoid circular dependency (#1270)

  • breaking(deps): require svelte 5.46.4 or later (#1271)

Patch Changes

  • chore: upgrade vitefu to compatible peer dependency range (#1286)

  • remove author field from package.json (#1281)

@benmccann benmccann force-pushed the changeset-release/main branch from b8baef3 to 4882d14 Compare February 23, 2026 19:09
@benmccann benmccann merged commit 67721b6 into main Feb 23, 2026
6 of 7 checks passed
@benmccann benmccann deleted the changeset-release/main branch February 23, 2026 19:14
@timmywil
Copy link

It probably would have been best to wait to release a stable version that required vite 8 until vite 8 was out of beta. This took me a while to debug.

@benmccann
Copy link
Member

Yeah, in retrospect I think you're right. I realized it afterwards. I'm not used to doing these releases - so lesson learned for next time

@benmccann
Copy link
Member

We just changed the latest tag on npm back to the 6.x branch. That should solve the issue of people being notified about the upgrade

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