Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): Bump @vue/eslint-config-typescript from 14.2.0 to 14.4.0 #3536

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 10, 2025

Bumps @vue/eslint-config-typescript from 14.2.0 to 14.4.0.

Release notes

Sourced from @​vue/eslint-config-typescript's releases.

v14.4.0

What's Changed

Full Changelog: vuejs/eslint-config-typescript@v14.3.0...v14.4.0

v14.3.0

New Features

  • A completely new approach to set up the ESLint configurations with helpers like defineConfigWithVueTs and vueTsConfigs. Please read the documentation for more details. With this new API set, you can easily override type-aware linting rules without worrying its position in the config array. Therefore there would be fewer mysterious errors or slowdown in a heavily customized project.

[!NOTE] The old style ...vueTsEslintConfig() still works, there's no need to update to the new style if that has been working well in your project.

Bug Fixes

New Contributors

Full Changelog: vuejs/eslint-config-typescript@v14.2.0...v14.3.0

Commits
  • e0ca842 14.4.0
  • 9af0a59 chore: dependency maintenance
  • 63853bd chore(deps): update dependency unplugin-vue-router to ^0.11.2 (#140)
  • d7818bb chore(deps): update dependency vitest to v3.0.5 [security] (#141)
  • 7cacc3e chore(deps): update vite packages (#138)
  • c7803b1 chore(deps): update all non-major dependencies (#139)
  • 98f56ad fix: proper support for extends field, fixes #136 (#143)
  • 9a1ed8a feat: optional tsSyntaxInTemplates; so that linting can be sped up by disab...
  • d23d94c chore(deps): update dependency vite to ^6.0.10 (#125)
  • f89d834 chore(deps): update dependency vitest to v3 (#134)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot requested a review from a team as a code owner February 10, 2025 22:29
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 10, 2025
@dependabot dependabot bot requested review from johncowen and removed request for a team February 10, 2025 22:29
Copy link

netlify bot commented Feb 10, 2025

Deploy Preview for kuma-gui ready!

Name Link
🔨 Latest commit 05c7cb8
🔍 Latest deploy log https://app.netlify.com/sites/kuma-gui/deploys/67af09d9497f090008721158
😎 Deploy Preview https://deploy-preview-3536--kuma-gui.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vue/eslint-config-typescript-14.4.0 branch 2 times, most recently from ec9129d to 304751a Compare February 11, 2025 10:56
@schogges schogges force-pushed the dependabot/npm_and_yarn/vue/eslint-config-typescript-14.4.0 branch from 2fa6afe to a91f419 Compare February 12, 2025 09:07
@schogges
Copy link
Contributor

schogges commented Feb 12, 2025

@johncowen please have a look 🙂

The original diff was just bumping the version in both package.json and package-lock.json, but didn't install the new version.

diff

package.json

"@stylistic/eslint-plugin": "^3.0.1",
"@typescript-eslint/eslint-plugin": "^8.23.0",
"@typescript-eslint/parser": "^8.23.0",
-"@vue/eslint-config-typescript": "^14.3.0",
+"@vue/eslint-config-typescript": "^14.4.0",
"esbuild": "^0.25.0",
"eslint-import-resolver-alias": "^1.1.2",
"eslint-import-resolver-typescript": "^3.7.0",

package-lock.json

"@stylistic/eslint-plugin": "^3.0.1",
"@typescript-eslint/eslint-plugin": "^8.23.0",
"@typescript-eslint/parser": "^8.23.0",
-"@vue/eslint-config-typescript": "^14.3.0",
+"@vue/eslint-config-typescript": "^14.4.0",
"esbuild": "^0.25.0",
"eslint-import-resolver-alias": "^1.1.2",
"eslint-import-resolver-typescript": "^3.7.0",

I checked for the installed version and was still on 14.2.0

kuma-gui
└─┬ @kumahq/[email protected] -> ./packages/config
  └── @vue/[email protected] invalid: "^14.4.0" from packages/config

After reinstalling @vue/eslint-config-typescript it's now on the correct version and the lock-file seems to properly updated.

kuma-gui
└─┬ @kumahq/[email protected] -> ./packages/config
  └── @vue/[email protected]

Bumps [@vue/eslint-config-typescript](https://github.com/vuejs/eslint-config-typescript) from 14.2.0 to 14.4.0.
- [Release notes](https://github.com/vuejs/eslint-config-typescript/releases)
- [Commits](vuejs/eslint-config-typescript@v14.2.0...v14.4.0)

---
updated-dependencies:
- dependency-name: "@vue/eslint-config-typescript"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@schogges schogges force-pushed the dependabot/npm_and_yarn/vue/eslint-config-typescript-14.4.0 branch from a91f419 to 29ce1fc Compare February 12, 2025 09:58
Signed-off-by: schogges <[email protected]>
@schogges schogges force-pushed the dependabot/npm_and_yarn/vue/eslint-config-typescript-14.4.0 branch from 29ce1fc to 3b325d2 Compare February 12, 2025 10:07
@johncowen
Copy link
Contributor

I briefly read the comment and I'm not sure if I totally follow, but wondered if our npm version changes from today have helped here at all?

@schogges
Copy link
Contributor

schogges commented Feb 12, 2025

I briefly read the comment and I'm not sure if I totally follow, but wondered if our npm version changes from today have helped here at all?

Not sure if it helped, we'd have to check how dependabot works with that. I just noticed here that the version have been bumped in both package and package-lock, but it didn't include the actual new version specs (and potential updated transitive dependencies), so i.e. expected to see the following

"node_modules/@vue/eslint-config-typescript": {
- "version": "14.2.0",
- "resolved": "https://registry.npmjs.org/@vue/eslint-config-typescript/-/eslint-config-typescript-14.2.0.tgz",
- "integrity": "sha512-JJ4wHuTJa2faQsBOUeWzuHOSFizVS7RWG2eH2noABk2LcT4wVcTOMZKM/lFobKBcgwADIPAKVRGFHVKooXImoA==",
+ "version": "14.4.0",
+ "resolved": "https://registry.npmjs.org/@vue/eslint-config-typescript/-/eslint-config-typescript-14.4.0.tgz",
+ "integrity": "sha512-daU+eAekEeVz3CReE4PRW25fe+OJDKwE28jHN6LimDEnuFMbJ6H4WGogEpNof276wVP6UvzOeJQfLFjB5mW29A==",

@schogges
Copy link
Contributor

I gave it a quick shot and it still doesn't update properly with [email protected] and [email protected] 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file production
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants