dev-KPI / messenger-backend

🦾 Back-end part of the messenger application.
https://messenger-backend.fly.dev/
MIT License
1 stars 0 forks source link

Bump lint-staged from 14.0.1 to 15.2.0 #48

Open dependabot[bot] opened 11 months ago

dependabot[bot] commented 11 months ago

Bumps lint-staged from 14.0.1 to 15.2.0.

Release notes

Sourced from lint-staged's releases.

v15.2.0

Minor Changes

  • #1371 f3378be Thanks @​iiroj! - Using the --no-stash flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag --no-hide-partially-staged that is automatically enabled when --no-stash is used.

Patch Changes

  • #1362 17bc480 Thanks @​antonk52! - update lilconfig@3.0.0

  • #1368 7c55ca9 Thanks @​iiroj! - Update most dependencies

  • #1368 777d4e9 Thanks @​iiroj! - To improve performance, only use lilconfig when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.

  • #1373 85eb0dd Thanks @​iiroj! - When determining git directory, use fs.realpath() only for symlinks. It looks like fs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.

v15.1.0

Minor Changes

  • #1344 0423311 Thanks @​danielbayley! - Add support for loading configuration from package.yaml and package.yml files, supported by pnpm.

Patch Changes

v15.0.2

Patch Changes

  • #1339 8e82364 Thanks @​iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.

v15.0.1

Patch Changes

  • #1217 d2e6f8b Thanks @​louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.

v15.0.0

Major Changes

  • #1322 66b93aa Thanks @​iiroj! - Require at least Node.js 18.12.0

    This release drops support for Node.js 16, which is EOL after 2023-09-11. Please upgrade your Node.js to the latest version.

    Additionally, all dependencies have been updated to their latest versions.

Changelog

Sourced from lint-staged's changelog.

15.2.0

Minor Changes

  • #1371 f3378be Thanks @​iiroj! - Using the --no-stash flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag --no-hide-partially-staged that is automatically enabled when --no-stash is used.

Patch Changes

  • #1362 17bc480 Thanks @​antonk52! - update lilconfig@3.0.0

  • #1368 7c55ca9 Thanks @​iiroj! - Update most dependencies

  • #1368 777d4e9 Thanks @​iiroj! - To improve performance, only use lilconfig when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.

  • #1373 85eb0dd Thanks @​iiroj! - When determining git directory, use fs.realpath() only for symlinks. It looks like fs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.

15.1.0

Minor Changes

  • #1344 0423311 Thanks @​danielbayley! - Add support for loading configuration from package.yaml and package.yml files, supported by pnpm.

Patch Changes

15.0.2

Patch Changes

  • #1339 8e82364 Thanks @​iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.

15.0.1

Patch Changes

  • #1217 d2e6f8b Thanks @​louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.

15.0.0

Major Changes

  • #1322 66b93aa Thanks @​iiroj! - Require at least Node.js 18.12.0

    This release drops support for Node.js 16, which is EOL after 2023-09-11. Please upgrade your Node.js to the latest version.

    Additionally, all dependencies have been updated to their latest versions.

Commits
  • adf50b0 chore(changeset): release
  • 85eb0dd fix: when determining git directory, use fs.realpath() only for symlinks
  • 82eded4 refactor: use commander implies() syntax for flag
  • f3378be feat: --no-stash flag implies --no-hide-partially-staged
  • f4f61f3 docs: add workaround for verbose Windows output to README FAQ
  • 17bc480 chore(deps): update lilconfig@3.0.0
  • eccda41 style: remove Babel from ESLint
  • 077e6bc test: run Jest tests in native ESM mode
  • 8db4a15 refactor: move config file name constants to separate file
  • 78a0c23 test: add missing test coverage
  • 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 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)