Skip to content

fix(deps): update all non-major dependencies #195

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 12, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/jest (source) 29.5.12 -> 29.5.14 age adoption passing confidence
husky 9.0.11 -> 9.1.7 age adoption passing confidence
lint-staged 15.2.6 -> 15.5.2 age adoption passing confidence
prettier (source) 3.3.2 -> 3.5.3 age adoption passing confidence
pretty-quick 4.0.0 -> 4.2.2 age adoption passing confidence
ts-jest (source) 29.1.4 -> 29.3.4 age adoption passing confidence
typescript (source) 5.4.5 -> 5.8.3 age adoption passing confidence
workbox-webpack-plugin (source) 7.1.0 -> 7.3.0 age adoption passing confidence

Release Notes

typicode/husky (husky)

v9.1.7

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.6...v9.1.7

v9.1.6

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.5...v9.1.6

v9.1.5

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.4...v9.1.5

v9.1.4

Compare Source

  • Improve deprecation notice

v9.1.3

Compare Source

  • fix: better handle space in PATH

v9.1.2

Compare Source

Show a message instead of automatically removing deprecated code.

This only concerns projects that still have the following code in their hooks:

- #!/usr/bin/env sh # <- This is deprecated, remove it
- . "$(dirname -- "$0")/_/husky.sh"  # <- This is deprecated, remove it

### Rest of your hook code

Hooks with these lines will fail in v10.0.0

v9.1.1

Compare Source

Super saiyan god dog! It's over 9.0.0!

What's new

You can now run package commands directly, no need for npx or equivalents.
It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again

For more advanced use cases, see lint-staged.

Fixes

  • bunx husky init command
  • Workaround for some hooks implementation on Windows

Deprecations

  • #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" are deprecated. husky command will automatically remove them, no action required.
  • If you're having code in ~/.huskyrc please move it to .config/husky/init.sh

Support for these will be removed in v10.

Friendly reminder

If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.

I've seen some confusion about this on X, so just a heads-up!

Sponsoring

Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.

Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉

v9.1.0

Compare Source

lint-staged/lint-staged (lint-staged)

v15.5.2

Compare Source

Patch Changes

v15.5.1

Compare Source

Patch Changes
  • #​1533 5d53534 Thanks @​iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:

    ✖ Failed to get staged files!
    

v15.5.0

Compare Source

Minor Changes
  • #​1526 630af5f Thanks @​iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.
Example with Prettier

By default Prettier prefers double quotes.

Previously
  1. Stage file.js with only double quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
  5. Commit was not done, original state is restored and single quotes ' are staged
Now
  1. Stage file.js with only double-quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails and cancels the commit
  5. Commit was not done, and there are no staged changes

v15.4.3

Compare Source

Patch Changes
  • #​1512 cbfed1d Thanks @​tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

v15.4.2

Compare Source

Patch Changes
  • #​1509 8827ebf Thanks @​iiroj! - Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.

v15.4.1

Compare Source

Patch Changes

v15.4.0

Compare Source

Minor Changes
  • #​1500 a8ec1dd Thanks @​iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:

    /**
     * @&#8203;filename: lint-staged.config.js
     * @&#8203;type {import('lint-staged').Configuration}
     */
    export default {
      '*': 'prettier --write',
    }

    It's also possible to use the .ts file extension for the configuration if your Node.js version supports it. The --experimental-strip-types flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.

    export NODE_OPTIONS="--experimental-strip-types"
    
    npx lint-staged --config lint-staged.config.ts
Patch Changes

v15.3.0

Compare Source

Minor Changes
  • #​1495 e69da9e Thanks @​iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.

  • #​1493 fa0fe98 Thanks @​iiroj! - Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

    For example:

    % npx lint-staged
    ✔ Backed up original state in git stash (20addf8)
    ✔ Running tasks for staged files...
    ✔ Applying modifications from tasks...
    ✔ Cleaning up temporary files...
    

    where the backup can be seen with git show 20addf8, or git stash list:

    % git stash list
    stash@{0}: lint-staged automatic backup (20addf8)
    

v15.2.11

Compare Source

Patch Changes
  • #​1484 bcfe309 Thanks @​wormsik! - Escape paths containing spaces when using the "shell" option.

  • #​1487 7dd8caa Thanks @​iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

v15.2.10

Compare Source

Patch Changes

v15.2.9

Compare Source

Patch Changes
  • #​1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Compare Source

Patch Changes
  • f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

    The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

v15.2.7

Compare Source

Patch Changes
  • #​1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.
prettier/prettier (prettier)

v3.5.3

Compare Source

v3.5.2

Compare Source

diff

Remove module-sync condition (#​17156 by @​fisker)

In Prettier 3.5.0, we added module-sync condition to package.json, so that require("prettier") can use ESM version, but turns out it doesn't work if CommonJS and ESM plugins both imports builtin plugins. To solve this problem, we decide simply remove the module-sync condition, so require("prettier") will still use the CommonJS version, we'll revisit until require(ESM) feature is more stable.

v3.5.1

Compare Source

diff

Fix CLI crash when cache for old version exists (#​17100 by @​sosukesuzuki)

Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.

Support dockercompose and github-actions-workflow in VSCode (#​17101 by @​remcohaszing)

Prettier now supports the dockercompose and github-actions-workflow languages in Visual Studio Code.

v3.5.0

Compare Source

diff

🔗 Release Notes

v3.4.2

Compare Source

diff

Treat U+30A0 & U+30FB in Katakana Block as CJK (#​16796 by @​tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->

C言
語
・
C++
・
Go
・
Rust

<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust

<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).

Fix comments print on class methods with decorators (#​16891 by @​fisker)
// Input
class A {
  @&#8203;decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @&#8203;decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @&#8203;decorator
  /**
   * The method description
   *
   */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}
Fix non-idempotent formatting (#​16899 by @​seiyab)

This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.

// Input
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.1 (first)
<div>
  foo
  <span>
    longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
  </span>, abc
</div>;

// Prettier 3.4.1 (second)
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.2
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

v3.4.1

Compare Source

diff

Remove unnecessary parentheses around assignment in v-on (#​16887 by @​fisker)
<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

v3.4.0

Compare Source

diff

🔗 Release Notes

v3.3.3

Compare Source

diff

Add parentheses for nullish coalescing in ternary (#​16391 by @​cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);
Add parentheses for decorator expressions (#​16458 by @​y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@&#8203;(foo`tagged template`)
class X {}

// Prettier 3.3.2
@&#8203;foo`tagged template`
class X {}

// Prettier 3.3.3
@&#8203;(foo`tagged template`)
class X {}
Support @let declaration syntax (#​16474 by @​sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

@&#8203;let name = 'Frodo';

<h1>Dashboard for {{name}}</h1>
Hello, {{name}}

For more details, please refer to the excellent blog post by the Angular Team: Introducing @​let in Angular.

We also appreciate the Angular Team for kindly answering our questions to implement this feature.

prettier/pretty-quick (pretty-quick)

v4.2.2

Compare Source

Patch Changes

Full Changelog: prettier/pretty-quick@v4.2.1...v4.2.2

v4.2.1

Compare Source

Patch Changes

Full Changelog: prettier/pretty-quick@v4.2.0...v4.2.1

v4.2.0

Compare Source

Minor Changes

v4.1.1

Compare Source

Patch Changes

v4.1.0

Compare Source

Minor Changes
kulshekhar/ts-jest (ts-jest)

v29.3.4

Compare Source

Bug Fixes
  • fix: fix TsJestTransformerOptions type (3b11e29), closes #​4247
  • fix(cli): fix wrong path for preset creator fns (249eb2c)
  • fix(config): disable rewriteRelativeImportExtensions always (9b1f472), closes #​4855

v29.3.3

Compare Source

Bug Fixes

v29.3.2

Compare Source

Bug Fixes
  • fix: transpile js files from node_modules whenever Jest asks (968370e), closes #​4637

v29.3.1

Compare Source

Bug Fixes
  • fix: allow isolatedModules mode to have ts.Program under Node16/Next (25157eb)
  • fix: improve message for isolatedModules of ts-jest config (547eb6f)

v29.3.0

Compare Source

Features
  • feat: support hybrid module values for isolatedModules: true (f372121)
Bug Fixes
  • fix: set customConditions to undefined in TsCompiler (b091d70), closes #​4620
Code Refactoring
  • refactor: remove manual version checker (89458fc)
  • refactor: remove patching deps based on version checker (bac4c43)
  • refactor: deprecate RawCompilerOptions interface (2b1b6cd)
  • refactor: deprecate transform option isolatedModules (7dfef71)

v29.2.6

Compare Source

v29.2.5

Compare Source

v29.2.4

Compare Source

v29.2.3

Compare Source

v29.2.2

Compare Source

v29.2.1

Compare Source

v29.2.0

Compare Source

Bug Fixes
  • fix: don't show warning message with Node16/NodeNext (99c4f49), closes #​4266
Features
  • feat(cli): allow migrating cjs presets to transform config (22fb027)
  • feat(presets): add util functions to create ESM presets (06f78ed), close #​4200
  • feat(presets): add util functions to create CJS presets (f9cc3c0), close #​4200
Code refactoring
  • refactor: replace lodash deps with native js implementation (40f1708)
  • refactor: use TsJestTransformerOptions type everywhere possibly (7d001be)
  • refactor(cli): use new preset util functions to initialize test config (c2b56ca)
  • refactor(presets): use create preset util functions for cjs presets (922d6d0)
  • test: switch react-app to use Vite (827c8ad)

v29.1.5

Compare Source

microsoft/TypeScript (typescript)

v5.8.3

Compare Source

v5.8.2

Compare Source

v5.7.3: TypeScript 5.7.3

Compare Source

For release notes, check out the release announcement.

Downloads are available on npm

v5.7.2: TypeScript 5.7

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

v5.6.3: TypeScript 5.6.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.6.2: TypeScript 5.6

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.5.4: TypeScript 5.5.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.5.3: TypeScript 5.5.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.5.2: TypeScript 5.5

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

googlechrome/workbox (workbox-webpack-plugin)

v7.3.0: Workbox v7.3.0

Compare Source

v7.3.0

  • Critical dependency updates.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 650f87a to cd1687e Compare June 16, 2024 16:23
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.2.7 chore(deps): update all non-major dependencies Jun 16, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 9832ee3 to a4ad3e3 Compare June 20, 2024 18:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from ea76c9c to 84c9351 Compare July 8, 2024 17:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from e7cbe81 to 7b542af Compare July 13, 2024 17:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 3521d2d to 5ac42c8 Compare July 23, 2024 00:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from a9cb281 to 28fbef2 Compare August 1, 2024 10:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 28fbef2 to c9b8c82 Compare August 3, 2024 08:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c9b8c82 to 211ab29 Compare August 13, 2024 06:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from cfd26bd to c3520f0 Compare August 23, 2024 17:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3ad42a8 to 29cd0b2 Compare September 3, 2024 16:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 00c70b3 to 38bb375 Compare February 1, 2025 20:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 20a50d3 to c16790a Compare February 13, 2025 20:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 8b3adec to c9e79bd Compare February 28, 2025 19:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from af120b7 to 2e4d634 Compare March 4, 2025 21:39
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 1d81ff0 to 5e63b7e Compare March 17, 2025 18:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5e63b7e to c4d924b Compare March 24, 2025 07:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 1f79101 to e2f3f01 Compare April 5, 2025 02:25
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3769f61 to 7233b16 Compare April 13, 2025 10:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7233b16 to b1df3c8 Compare April 24, 2025 09:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b1df3c8 to 20605c6 Compare May 6, 2025 10:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 8b35ac4 to 88c8a94 Compare May 19, 2025 17:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 9afdf07 to 7af6116 Compare June 2, 2025 02:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7af6116 to 6e248cb Compare June 2, 2025 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants