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.

Sign up for GitHub

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

Jump to bottom

deps(deps-dev): bump the dependencies group across 1 directory with 11 updates #242

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

deps(deps-dev): bump the dependencies group across 1 directory with 11 updates #242

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 9, 2025

Bumps the dependencies group with 11 updates in the / directory:

Package From To
@lerna-lite/changed 3.10.0 3.11.0
@lerna-lite/cli 3.10.0 3.11.0
@lerna-lite/diff 3.10.0 3.11.0
@lerna-lite/exec 3.10.0 3.11.0
@lerna-lite/publish 3.10.0 3.11.0
@lerna-lite/run 3.10.0 3.11.0
@lerna-lite/version 3.10.0 3.11.0
eslint-import-resolver-typescript 3.6.3 3.7.0
prettier 3.3.3 3.4.2
typescript 5.6.3 5.7.3
@types/node 22.9.0 22.10.5

Updates @lerna-lite/changed from 3.10.0 to 3.11.0

Release notes

Sourced from @​lerna-lite/changed's releases.

v3.11.0

3.11.0 (2025-01-02)

📢 Lerna-Lite now provides partial support for the new pnpm catalog: protocol

Starting the New Year with a new feature :) Thanks to @​wassim-ben-amor and @​Mister-Hope for providing the code and a pull request for this new feature. However please note that it comes with certain limitations (as described in the Publish#catalog docs)

The catalog: protocol (pnpm catalog) can be recognized by Lerna-Lite. When publishing, they will be kept as is. If you need to bump the version of a package in a catalog, you will need to edit pnpm-workspace.yaml manually. So we suggest using workspace: protocol instead for workspace dependencies.

Also note that there are currently no unit tests for this new feature yet, we should eventually add unit tests but it was skipped for now to make the new feature available as quickly as possible. Getting a PR by anyone to add unit tests would be super welcome. Thanks again to @​wassim-ben-amor and @​Mister-Hope for this external contributions 🚀

[!NOTE] It seems that I misunderstood what the external PR for catalog: really does, it only makes lerna version happier (not crash as opposed to before) and users would have to execute pnpm publish instead of lerna publish for the catalog: to really be replaced. It would probably require more work in Lerna-Lite to fully support catalog: for both lerna commands (version/publish)... more to come I guess.

Features

Bug Fixes

v3.10.1

3.10.1 (2024-11-28)

Bug Fixes

Changelog

Sourced from @​lerna-lite/changed's changelog.

3.11.0 (2025-01-02)

Note: Version bump only for package @​lerna-lite/changed

3.10.1 (2024-11-28)

Note: Version bump only for package @​lerna-lite/changed

Commits
  • 2cf5915 chore(release): publish new version v3.11.0
  • 6aab9c5 chore: add missing git prefix on git repo links
  • a91533e chore(release): publish new version v3.10.1
  • See full diff in compare view

Updates @lerna-lite/cli from 3.10.0 to 3.11.0

Release notes

Sourced from @​lerna-lite/cli's releases.

v3.11.0

3.11.0 (2025-01-02)

📢 Lerna-Lite now provides partial support for the new pnpm catalog: protocol

Starting the New Year with a new feature :) Thanks to @​wassim-ben-amor and @​Mister-Hope for providing the code and a pull request for this new feature. However please note that it comes with certain limitations (as described in the Publish#catalog docs)

The catalog: protocol (pnpm catalog) can be recognized by Lerna-Lite. When publishing, they will be kept as is. If you need to bump the version of a package in a catalog, you will need to edit pnpm-workspace.yaml manually. So we suggest using workspace: protocol instead for workspace dependencies.

Also note that there are currently no unit tests for this new feature yet, we should eventually add unit tests but it was skipped for now to make the new feature available as quickly as possible. Getting a PR by anyone to add unit tests would be super welcome. Thanks again to @​wassim-ben-amor and @​Mister-Hope for this external contributions 🚀

[!NOTE] It seems that I misunderstood what the external PR for catalog: really does, it only makes lerna version happier (not crash as opposed to before) and users would have to execute pnpm publish instead of lerna publish for the catalog: to really be replaced. It would probably require more work in Lerna-Lite to fully support catalog: for both lerna commands (version/publish)... more to come I guess.

Features

Bug Fixes

v3.10.1

3.10.1 (2024-11-28)

Bug Fixes

Changelog

Sourced from @​lerna-lite/cli's changelog.

3.11.0 (2025-01-02)

Bug Fixes

3.10.1 (2024-11-28)

Note: Version bump only for package @​lerna-lite/cli

Commits
  • 2cf5915 chore(release): publish new version v3.11.0
  • 956ad09 fix(deps): update all non-major dependencies (#966)
  • 6aab9c5 chore: add missing git prefix on git repo links
  • a91533e chore(release): publish new version v3.10.1
  • See full diff in compare view

Updates @lerna-lite/diff from 3.10.0 to 3.11.0

Release notes

Sourced from @​lerna-lite/diff's releases.

v3.11.0

3.11.0 (2025-01-02)

📢 Lerna-Lite now provides partial support for the new pnpm catalog: protocol

Starting the New Year with a new feature :) Thanks to @​wassim-ben-amor and @​Mister-Hope for providing the code and a pull request for this new feature. However please note that it comes with certain limitations (as described in the Publish#catalog docs)

The catalog: protocol (pnpm catalog) can be recognized by Lerna-Lite. When publishing, they will be kept as is. If you need to bump the version of a package in a catalog, you will need to edit pnpm-workspace.yaml manually. So we suggest using workspace: protocol instead for workspace dependencies.

Also note that there are currently no unit tests for this new feature yet, we should eventually add unit tests but it was skipped for now to make the new feature available as quickly as possible. Getting a PR by anyone to add unit tests would be super welcome. Thanks again to @​wassim-ben-amor and @​Mister-Hope for this external contributions 🚀

[!NOTE] It seems that I misunderstood what the external PR for catalog: really does, it only makes lerna version happier (not crash as opposed to before) and users would have to execute pnpm publish instead of lerna publish for the catalog: to really be replaced. It would probably require more work in Lerna-Lite to fully support catalog: for both lerna commands (version/publish)... more to come I guess.

Features

Bug Fixes

v3.10.1

3.10.1 (2024-11-28)

Bug Fixes

Changelog

Sourced from @​lerna-lite/diff's changelog.

3.11.0 (2025-01-02)

Note: Version bump only for package @​lerna-lite/diff

3.10.1 (2024-11-28)

Note: Version bump only for package @​lerna-lite/diff

Commits
  • 2cf5915 chore(release): publish new version v3.11.0
  • 6aab9c5 chore: add missing git prefix on git repo links
  • a91533e chore(release): publish new version v3.10.1
  • See full diff in compare view

Updates @lerna-lite/exec from 3.10.0 to 3.11.0

Release notes

Sourced from @​lerna-lite/exec's releases.

v3.11.0

3.11.0 (2025-01-02)

📢 Lerna-Lite now provides partial support for the new pnpm catalog: protocol

Starting the New Year with a new feature :) Thanks to @​wassim-ben-amor and @​Mister-Hope for providing the code and a pull request for this new feature. However please note that it comes with certain limitations (as described in the Publish#catalog docs)

The catalog: protocol (pnpm catalog) can be recognized by Lerna-Lite. When publishing, they will be kept as is. If you need to bump the version of a package in a catalog, you will need to edit pnpm-workspace.yaml manually. So we suggest using workspace: protocol instead for workspace dependencies.

Also note that there are currently no unit tests for this new feature yet, we should eventually add unit tests but it was skipped for now to make the new feature available as quickly as possible. Getting a PR by anyone to add unit tests would be super welcome. Thanks again to @​wassim-ben-amor and @​Mister-Hope for this external contributions 🚀

[!NOTE] It seems that I misunderstood what the external PR for catalog: really does, it only makes lerna version happier (not crash as opposed to before) and users would have to execute pnpm publish instead of lerna publish for the catalog: to really be replaced. It would probably require more work in Lerna-Lite to fully support catalog: for both lerna commands (version/publish)... more to come I guess.

Features

Bug Fixes

v3.10.1

3.10.1 (2024-11-28)

Bug Fixes

Changelog

Sourced from @​lerna-lite/exec's changelog.

3.11.0 (2025-01-02)

Bug Fixes

3.10.1 (2024-11-28)

Note: Version bump only for package @​lerna-lite/exec

Commits
  • 2cf5915 chore(release): publish new version v3.11.0
  • 956ad09 fix(deps): update all non-major dependencies (#966)
  • 6aab9c5 chore: add missing git prefix on git repo links
  • a91533e chore(release): publish new version v3.10.1
  • ca7f9b9 chore(deps): update all non-major dependencies (#953)
  • See full diff in compare view

Updates @lerna-lite/publish from 3.10.0 to 3.11.0

Release notes

Sourced from @​lerna-lite/publish's releases.

v3.11.0

3.11.0 (2025-01-02)

📢 Lerna-Lite now provides partial support for the new pnpm catalog: protocol

Starting the New Year with a new feature :) Thanks to @​wassim-ben-amor and @​Mister-Hope for providing the code and a pull request for this new feature. However please note that it comes with certain limitations (as described in the Publish#catalog docs)

The catalog: protocol (pnpm catalog) can be recognized by Lerna-Lite. When publishing, they will be kept as is. If you need to bump the version of a package in a catalog, you will need to edit pnpm-workspace.yaml manually. So we suggest using workspace: protocol instead for workspace dependencies.

Also note that there are currently no unit tests for this new feature yet, we should eventually add unit tests but it was skipped for now to make the new feature available as quickly as possible. Getting a PR by anyone to add unit tests would be super welcome. Thanks again to @​wassim-ben-amor and @​Mister-Hope for this external contributions 🚀

[!NOTE] It seems that I misunderstood what the external PR for catalog: really does, it only makes lerna version happier (not crash as opposed to before) and users would have to execute pnpm publish instead of lerna publish for the catalog: to really be replaced. It would probably require more work in Lerna-Lite to fully support catalog: for both lerna commands (version/publish)... more to come I guess.

Features

Bug Fixes

v3.10.1

3.10.1 (2024-11-28)

Bug Fixes

Changelog

Sourced from @​lerna-lite/publish's changelog.

3.11.0 (2025-01-02)

Features

Bug Fixes

3.10.1 (2024-11-28)

Note: Version bump only for package @​lerna-lite/publish

Commits
  • 2cf5915 chore(release): publish new version v3.11.0
  • 956ad09 fix(deps): update all non-major dependencies (#966)
  • 4d739e2 feat(core): support catalog: protocol (#965)
  • 6aab9c5 chore: add missing git prefix on git repo links
  • a91533e chore(release): publish new version v3.10.1
  • ca7f9b9 chore(deps): update all non-major dependencies (#953)
  • See full diff in compare view

Updates @lerna-lite/run from 3.10.0 to 3.11.0

Release notes

Sourced from @​lerna-lite/run's releases.

v3.11.0

3.11.0 (2025-01-02)

📢 Lerna-Lite now provides partial support for the new pnpm catalog: protocol

Starting the New Year with a new feature :) Thanks to @​wassim-ben-amor and @​Mister-Hope for providing the code and a pull request for this new feature. However please note that it comes with certain limitations (as described in the Publish#catalog docs)

The catalog: protocol (pnpm catalog) can be recognized by Lerna-Lite. When publishing, they will be kept as is. If you need to bump the version of a package in a catalog, you will need to edit pnpm-workspace.yaml manually. So we suggest using workspace: protocol instead for workspace dependencies.

Also note that there are currently no unit tests for this new feature yet, we should eventually add unit tests but it was skipped for now to make the new feature available as quickly as possible. Getting a PR by anyone to add unit tests would be super welcome. Thanks again to @​wassim-ben-amor and @​Mister-Hope for this external contributions 🚀

[!NOTE] It seems that I misunderstood what the external PR for catalog: really does, it only makes lerna version happier (not crash as opposed to before) and users would have to execute pnpm publish instead of lerna publish for the catalog: to really be replaced. It would probably require more work in Lerna-Lite to fully support catalog: for both lerna commands (version/publish)... more to come I guess.

Features

Bug Fixes

v3.10.1

3.10.1 (2024-11-28)

Bug Fixes

Changelog

Sourced from @​lerna-lite/run's changelog.

3.11.0 (2025-01-02)

Bug Fixes

3.10.1 (2024-11-28)

Note: Version bump only for package @​lerna-lite/run

Commits
  • 2cf5915 chore(release): publish new version v3.11.0
  • 956ad09 fix(deps): update all non-major dependencies (#966)
  • 6aab9c5 chore: add missing git prefix on git repo links
  • a91533e chore(release): publish new version v3.10.1
  • ca7f9b9 chore(deps): update all non-major dependencies (#953)
  • See full diff in compare view

Updates @lerna-lite/version from 3.10.0 to 3.11.0

Release notes

Sourced from @​lerna-lite/version's releases.

v3.11.0

3.11.0 (2025-01-02)

📢 Lerna-Lite now provides partial support for the new pnpm catalog: protocol

Starting the New Year with a new feature :) Thanks to @​wassim-ben-amor and @​Mister-Hope for providing the code and a pull request for this new feature. However please note that it comes with certain limitations (as described in the Publish#catalog docs)

The catalog: protocol (pnpm catalog) can be recognized by Lerna-Lite. When publishing, they will be kept as is. If you need to bump the version of a package in a catalog, you will need to edit pnpm-workspace.yaml manually. So we suggest using workspace: protocol instead for workspace dependencies.

Also note that there are currently no unit tests for this new feature yet, we should eventually add unit tests but it was skipped for now to make the new feature available as quickly as possible. Getting a PR by anyone to add unit tests would be super welcome. Thanks again to @​wassim-ben-amor and @​Mister-Hope for this external contributions 🚀

[!NOTE] It seems that I misunderstood what the external PR for catalog: really does, it only makes lerna version happier (not crash as opposed to before) and users would have to execute pnpm publish instead of lerna publish for the catalog: to really be replaced. It would probably require more work in Lerna-Lite to fully support catalog: for both lerna commands (version/publish)... more to come I guess.

Features

Bug Fixes

v3.10.1

3.10.1 (2024-11-28)

Bug Fixes

Changelog

Sourced from @​lerna-lite/version's changelog.

3.11.0 (2025-01-02)

Bug Fixes

3.10.1 (2024-11-28)

Bug Fixes

Commits
  • 2cf5915 chore(release): publish new version v3.11.0
  • 956ad09 fix(deps): update all non-major dependencies (#966)
  • 6aab9c5 chore: add missing git prefix on git repo links
  • a91533e chore(release): publish new version v3.10.1
  • e48a19a chore(deps): update all non-major dependencies (#962)
  • c4d1833 fix(deps): update dependency git-url-parse to v16 (#960)
  • cbda4b6 fix(deps): update dependency uuid to v11 (#957)
  • 2f23996 fix: drop strip-ansi in favor of native stripVTControlCharacters (#950)
  • See full diff in compare view

Updates eslint-import-resolver-typescript from 3.6.3 to 3.7.0

Release notes

Sourced from eslint-import-resolver-typescript's releases.

v3.7.0

Minor Changes

  • #326 93ea130 Thanks @​SukkaW! - This version has implemented the eslint-plugin-import-x's v3 resolver interface. This allows you to use import/require to reference eslint-import-resolver-typescript directly in your ESLint flat config:

    Previously

    // eslint.config.js
module.exports = {
  settings: {
    'import-x/resolver': {
      typescript: {
        alwaysTryTypes: true,
      },
      // or
      require.resolve('eslint-import-resolver-typescript'):
        alwaysTryTypes: true,
      }
    }
  }
}

    Now

    // eslint.config.js
const {
  createTypeScriptImportResolver,
} = require('eslint-import-resolver-typescript')
module.exports = {
settings: {
'import-x/resolver-next': [
createTypeScriptImportResolver({
alwaysTryTypes: true,
}),
],
},
}

    Note that this only works with eslint-plugin-import-x@>=4.5.0. You can't use createTypeScriptImportResolver with the older versions of eslint-plugin-import-x or any existing versions of eslint-plugin-import.

Changelog

Sourced from eslint-import-resolver-typescript's changelog.

3.7.0

Minor Changes

  • #326 93ea130 Thanks @​SukkaW! - This version has implemented the eslint-plugin-import-x's v3 resolver interface. This allows you to use import/require to reference eslint-import-resolver-typescript directly in your ESLint flat config:

    Previously

    // eslint.config.js
module.exports = {
  settings: {
    'import-x/resolver': {
      typescript: {
        alwaysTryTypes: true,
      },
      // or
      require.resolve('eslint-import-resolver-typescript'):
        alwaysTryTypes: true,
      }
    }
  }
}

    Now

    // eslint.config.js
const {
  createTypeScriptImportResolver,
} = require('eslint-import-resolver-typescript')
module.exports = {
settings: {
'import-x/resolver-next': [
createTypeScriptImportResolver({
alwaysTryTypes: true,
}),
],
},
}

    Note that this only works with eslint-plugin-import-x@>=4.5.0. You can't use createTypeScriptImportResolver with the older versions of eslint-plugin-import-x or any existing versions of eslint-plugin-import.

Commits
  • c5da700 chore: release eslint-import-resolver-typescript (#327)
  • 93ea130 feat: implement import-x resolver interface v3 (#326)
  • e6256b7 chore(deps): update dependency simple-git-hooks to ^2.11.1 (#325)
  • da56f17 chore(deps): update dependency react to ^18.3.1 (#324)
  • 88a6d44 chore(deps): update node.js to v18.20.5 (#323)
  • bed664f chore(deps): update dependency @​changesets/cli to ^2.27.10 (#322)
  • 42e7cc3 chore(deps): update dependency @​types/node to ^18.19.63 (#320)
  • 13fa760 chore(deps): update dependency @​changesets/cli to ^2.27.9 (#319)
  • 5ee5879 fix(deps): update dependency debug to ^4.3.7 (#316)
  • f5b09f5 chore(deps): update dependency eslint to ^8.57.1 (#315)
  • Additional commits viewable in compare view

Updates prettier from 3.3.3 to 3.4.2

Release notes

Sourced from prettier's releases.

3.4.2

🔗 Changelog

3.4.1

🔗 Changelog

3.4.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.4.2

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

Description has been truncated

@dependabot
deps(deps-dev): bump the dependencies group across 1 directory with 1…
d618c73 
…1 updates

Bumps the dependencies group with 11 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@lerna-lite/changed](https://github.com/lerna-lite/lerna-lite/tree/HEAD/packages/changed) | `3.10.0` | `3.11.0` |
| [@lerna-lite/cli](https://github.com/lerna-lite/lerna-lite/tree/HEAD/packages/cli) | `3.10.0` | `3.11.0` |
| [@lerna-lite/diff](https://github.com/lerna-lite/lerna-lite/tree/HEAD/packages/diff) | `3.10.0` | `3.11.0` |
| [@lerna-lite/exec](https://github.com/lerna-lite/lerna-lite/tree/HEAD/packages/exec) | `3.10.0` | `3.11.0` |
| [@lerna-lite/publish](https://github.com/lerna-lite/lerna-lite/tree/HEAD/packages/publish) | `3.10.0` | `3.11.0` |
| [@lerna-lite/run](https://github.com/lerna-lite/lerna-lite/tree/HEAD/packages/run) | `3.10.0` | `3.11.0` |
| [@lerna-lite/version](https://github.com/lerna-lite/lerna-lite/tree/HEAD/packages/version) | `3.10.0` | `3.11.0` |
| [eslint-import-resolver-typescript](https://github.com/import-js/eslint-import-resolver-typescript) | `3.6.3` | `3.7.0` |
| [prettier](https://github.com/prettier/prettier) | `3.3.3` | `3.4.2` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.6.3` | `5.7.3` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `22.9.0` | `22.10.5` |



Updates `@lerna-lite/changed` from 3.10.0 to 3.11.0
- [Release notes](https://github.com/lerna-lite/lerna-lite/releases)
- [Changelog](https://github.com/lerna-lite/lerna-lite/blob/main/packages/changed/CHANGELOG.md)
- [Commits](https://github.com/lerna-lite/lerna-lite/commits/v3.11.0/packages/changed)

Updates `@lerna-lite/cli` from 3.10.0 to 3.11.0
- [Release notes](https://github.com/lerna-lite/lerna-lite/releases)
- [Changelog](https://github.com/lerna-lite/lerna-lite/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/lerna-lite/lerna-lite/commits/v3.11.0/packages/cli)

Updates `@lerna-lite/diff` from 3.10.0 to 3.11.0
- [Release notes](https://github.com/lerna-lite/lerna-lite/releases)
- [Changelog](https://github.com/lerna-lite/lerna-lite/blob/main/packages/diff/CHANGELOG.md)
- [Commits](https://github.com/lerna-lite/lerna-lite/commits/v3.11.0/packages/diff)

Updates `@lerna-lite/exec` from 3.10.0 to 3.11.0
- [Release notes](https://github.com/lerna-lite/lerna-lite/releases)
- [Changelog](https://github.com/lerna-lite/lerna-lite/blob/main/packages/exec/CHANGELOG.md)
- [Commits](https://github.com/lerna-lite/lerna-lite/commits/v3.11.0/packages/exec)

Updates `@lerna-lite/publish` from 3.10.0 to 3.11.0
- [Release notes](https://github.com/lerna-lite/lerna-lite/releases)
- [Changelog](https://github.com/lerna-lite/lerna-lite/blob/main/packages/publish/CHANGELOG.md)
- [Commits](https://github.com/lerna-lite/lerna-lite/commits/v3.11.0/packages/publish)

Updates `@lerna-lite/run` from 3.10.0 to 3.11.0
- [Release notes](https://github.com/lerna-lite/lerna-lite/releases)
- [Changelog](https://github.com/lerna-lite/lerna-lite/blob/main/packages/run/CHANGELOG.md)
- [Commits](https://github.com/lerna-lite/lerna-lite/commits/v3.11.0/packages/run)

Updates `@lerna-lite/version` from 3.10.0 to 3.11.0
- [Release notes](https://github.com/lerna-lite/lerna-lite/releases)
- [Changelog](https://github.com/lerna-lite/lerna-lite/blob/main/packages/version/CHANGELOG.md)
- [Commits](https://github.com/lerna-lite/lerna-lite/commits/v3.11.0/packages/version)

Updates `eslint-import-resolver-typescript` from 3.6.3 to 3.7.0
- [Release notes](https://github.com/import-js/eslint-import-resolver-typescript/releases)
- [Changelog](https://github.com/import-js/eslint-import-resolver-typescript/blob/master/CHANGELOG.md)
- [Commits](import-js/eslint-import-resolver-typescript@v3.6.3...v3.7.0)

Updates `prettier` from 3.3.3 to 3.4.2
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.3.3...3.4.2)

Updates `typescript` from 5.6.3 to 5.7.3
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml)
- [Commits](microsoft/TypeScript@v5.6.3...v5.7.3)

Updates `@types/node` from 22.9.0 to 22.10.5
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@lerna-lite/changed"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@lerna-lite/cli"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@lerna-lite/diff"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@lerna-lite/exec"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@lerna-lite/publish"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@lerna-lite/run"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@lerna-lite/version"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: eslint-import-resolver-typescript
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: prettier
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: typescript
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from alimd as a code owner January 9, 2025 00:29
@dependabot dependabot bot added ci Work that improves the continuous integration. dependencies Change in project dependencies. maintenance Generic maintenance tasks. priority-low Nice addition, maybe... someday... labels Jan 9, 2025
@dependabot dependabot bot mentioned this pull request Jan 9, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alimd alimd Awaiting requested review from alimd alimd is a code owner

At least 0 approving reviews are required to merge this pull request.

Assignees
No one assigned
Labels
ci Work that improves the continuous integration. dependencies Change in project dependencies. maintenance Generic maintenance tasks. priority-low Nice addition, maybe... someday...
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants