Bump eslint-plugin-svelte from 3.10.1 to 3.13.0 #379
                
     Closed
            
            
          
  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.
  
    
  
    
Bumps eslint-plugin-svelte from 3.10.1 to 3.13.0.
Release notes
Sourced from eslint-plugin-svelte's releases.
... (truncated)
Changelog
Sourced from eslint-plugin-svelte's changelog.
... (truncated)
Commits
6e68978chore: release eslint-plugin-svelte (#1411)005e9fdfix(no-navigation-without-resolve): allowing undefined and null in link hrefs...074af20feat(no-navigation-without-resolve): checking link shorthand attributes (#1323)881fee7chore: release eslint-plugin-svelte (#1379)e4d788dchore: usepnpm-lock.yamlandminimumReleaseAge(#1403)2d72bf1fix: update fixture5ba5c3efix(no-unused-props): validate spread operator properly (#1378)27cf677fix(no-navigation-without-resolve): improve error messages (#1377)57ccf95fix(no-navigation-without-resolve): Detecting asset() function as well (#1365)98fc478chore: ranpnpm test:update-fixturesto update YAML files (#1374)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for eslint-plugin-svelte since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)