neo-ltex / vscode-ltex

LTeX: Grammar/spell checker :mag::heavy_check_mark: for VS Code using LanguageTool with support for LaTeX :mortar_board:, Markdown :pencil:, and others
https://valentjn.github.io/ltex
Mozilla Public License 2.0
16 stars 1 forks source link

chore(deps): bump the npm_and_yarn group across 1 directory with 3 updates #78

Open dependabot[bot] opened 3 months ago

dependabot[bot] commented 3 months ago

Bumps the npm_and_yarn group with 3 updates in the / directory: tar, nanoid and mocha.

Updates tar from 6.2.0 to 6.2.1

Commits


Removes nanoid

Updates mocha from 9.1.3 to 9.2.2

Release notes

Sourced from mocha's releases.

v9.2.2

9.2.2 / 2022-03-11

Please also note our announcements.

:bug: Fixes

:nut_and_bolt: Other

v9.2.1

9.2.1 / 2022-02-19

Please also note our announcements.

:bug: Fixes

v9.2.0

9.2.0 / 2022-01-24

Please also note our announcements.

:tada: Enhancements

:nut_and_bolt: Other

v9.1.4

9.1.4 / 2022-01-14

Please also note our announcements.

:bug: Fixes

:nut_and_bolt: Other

... (truncated)

Changelog

Sourced from mocha's changelog.

9.2.2 / 2022-03-11

:bug: Fixes

:nut_and_bolt: Other

9.2.1 / 2022-02-19

:bug: Fixes

9.2.0 / 2022-01-24

:tada: Enhancements

:nut_and_bolt: Other

9.1.4 / 2022-01-14

:bug: Fixes

:nut_and_bolt: Other

Commits
  • 24b5243 build(v9.2.2): release
  • 22a1560 build(v9.2.2): update CHANGELOG [ci skip]
  • 632e602 chore: update dependencies (#4843)
  • 241964b fix: wrong error thrown while loading reporter (#4842)
  • 22f9306 fix(dry-run): potential call-stack crash with 'dry-run' option (#4839)
  • 547ffd7 build(v9.2.1): release
  • ca7432a build(v9.2.1): update CHANGELOG [ci skip]
  • 86305cf fix: wrong error thrown while loading config files (#4832)
  • 11c4560 fix: configurable max diff size (#4799)
  • 509938d doc: fix to show sponsors in narrow view (#4793)
  • Additional commits viewable in compare view


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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/neo-ltex/vscode-ltex/network/alerts).
changeset-bot[bot] commented 3 months ago

⚠️ No Changeset found

Latest commit: e91f4ca94085380c2d610e3c43eea10013edc565

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR