chore: release eslint-plugin-svelte (next) #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
[email protected]
Patch Changes
#1016
91999e3Thanks @baseballyama! - chore: change the rule category ofvalid-prop-names-in-kit-pagestoSvelteKit#1012
763cf7aThanks @baseballyama! - chore: change the rule category ofno-export-load-in-svelte-module-in-kit-pagestoSvelteKit#1017
806d72aThanks @baseballyama! - chore: do not runno-reactive-functionsrule on Svelte 5 with runes#1014
74373ecThanks @baseballyama! - chore: do not runno-reactive-reassignrule on Svelte 5 with runes#1018
5bdc906Thanks @baseballyama! - chore: run theno-inspectrule only in Svelte 5’s runes mode#1006
5fd91baThanks @baseballyama! - chore: do not runinfinite-reactive-looprule on Svelte 5 with runes