fix(deps): update dependencies (patch)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@arethetypeswrong/cli (source)	0.15.3 -> 0.15.4
@types/node (source)	20.14.9 -> 20.14.15
commitizen	4.3.0 -> 4.3.1
lint-staged	15.2.7 -> 15.2.11
npm-run-all2	6.2.0 -> 6.2.6
prettier (source)	3.3.2 -> 3.3.3
publint (source)	0.2.8 -> 0.2.12
typescript (source)	5.5.2 -> 5.5.4

---

Release Notes

arethetypeswrong/arethetypeswrong.github.io (@​arethetypeswrong/cli)

v0.15.4

Compare Source

Patch Changes

• 5566c1b: Upgrading marked-terminal to version 7.1.0

commitizen/cz-cli (commitizen)

v4.3.1

Compare Source

4.3.1 (2024-09-27)

Bug Fixes

• Close process after retry commit. Closes #​974 (#​1001) (3ce8dd5)

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

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

• #​1471 e3f283b Thanks @​iiroj! - Update minor dependencies, including micromatch@~4.0.8.

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.

bcomnes/npm-run-all2 (npm-run-all2)

v6.2.6

Compare Source

Commits

• Prevent a throw when looking up undefined results d928f9a

v6.2.5

Compare Source

v6.2.4

Compare Source

Merged

• Switch to JS-based which command #154

Fixed

• Switch to JS-based which command #153

v6.2.3

Compare Source

Commits

• Merge pull request #​151 from bcomnes/fix-pnpm-agian c43fa2b
• Avoid passing config fields as flags for pnpm dc2d7da

v6.2.2

Compare Source

Commits

• Revert "Compatibility: npm, yarn and pnpm run scripts" fc35f0d

v6.2.1

Compare Source

Merged

• Compatibility: npm, yarn and pnpm run scripts #143
• Use neostandard + add more static code analysis #142
• Upgrade: Bump c8 from 9.1.0 to 10.0.0 #141
• Upgrade: Bump p-queue from 7.4.1 to 8.0.1 #138

prettier/prettier (prettier)

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
@​(foo`tagged template`)
class X {}

// Prettier 3.3.2
@​foo`tagged template`
class X {}

// Prettier 3.3.3
@​(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:

@​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.

bluwy/publint (publint)

v0.2.12

Compare Source

Features

• If the package publishes a license file, but the "license" field is not set in package.json, a suggestion will now be shown to add the field (https://github.com/bluwy/publint/issues/111)

Bug fixes

• In the "repostory" field, string shorthands with nested paths like gitlab:org/user/repo is now considered valid (https://github.com/bluwy/publint/issues/113)

Site

• Fixed repository url link for string shorthands (https://github.com/bluwy/publint/issues/109)

Full Changelog: publint/publint@v0.2.11...v0.2.12

v0.2.11

Compare Source

Features

• Update formatMessage() utility with a new color option to force enable or disable returning color in string (https://github.com/bluwy/publint/pull/110)

New Contributors

• @​zanminkian made their first contribution in https://github.com/bluwy/publint/pull/110

Full Changelog: publint/publint@v0.2.10...v0.2.11

v0.2.10

Compare Source

Features

• Adds a new rule that validates the "repository" field (https://github.com/bluwy/publint/pull/106)
  • If "repository" is a string, it must be one of the supported shorthand strings from the docs.
  • If "repository" is an object with "type": "git", the "url" must be a valid git URL and can be parsed by npm.
  • The git:// protocol for GitHub repos should not be used due security concerns.
  • GitHub or GitLab links should be prefixed with git+ and postfixed with .git. (This is also warned by npm when publishing a package).

New Contributors

• @​Namchee made their first contribution in https://github.com/bluwy/publint/pull/106

Full Changelog: publint/publint@v0.2.9...v0.2.10

v0.2.9

Compare Source

Bug fixes

• Update message when no type field is present by @​benmccann (https://github.com/bluwy/publint/pull/104)

New Contributors

• @​benmccann made their first contribution in https://github.com/bluwy/publint/pull/104

Full Changelog: publint/publint@v0.2.8...v0.2.9

microsoft/TypeScript (typescript)

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

• fixed issues query for TypeScript v5.5.4 (Stable).
• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package (soon!)

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

• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package

---

Configuration

📅 Schedule: Branch creation - "on the 1st day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[kodiakhq]

This PR currently has a merge conflict. Please resolve this and then re-add the ['automerge'] label.