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.

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

Bump the app-deps group across 1 directory with 5 updates #628

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 9, 2024

Bumps the app-deps group with 5 updates in the / directory:

Package From To
@babel/preset-env 7.25.0 7.25.4
@types/node 22.0.0 22.5.4
@vscode/vsce 2.31.1 3.1.0
concurrently 8.2.2 9.0.0
esbuild 0.23.0 0.23.1

Updates @babel/preset-env from 7.25.0 to 7.25.4

Release notes

Sourced from @​babel/preset-env's releases.

v7.25.4 (2024-08-22)

🐛 Bug Fix

💅 Polish

  • babel-generator, babel-plugin-proposal-decorators, babel-plugin-proposal-destructuring-private, babel-plugin-proposal-pipeline-operator, babel-plugin-transform-class-properties, babel-plugin-transform-destructuring, babel-plugin-transform-optional-chaining, babel-plugin-transform-private-methods, babel-plugin-transform-private-property-in-object, babel-plugin-transform-typescript, babel-runtime-corejs2, babel-runtime, babel-traverse
  • babel-generator, babel-plugin-transform-class-properties
  • babel-generator, babel-plugin-proposal-decorators, babel-plugin-proposal-destructuring-private, babel-plugin-transform-object-rest-spread

🔬 Output optimization

Committers: 4

v7.25.3 (2024-07-31)

🐛 Bug Fix

  • babel-plugin-bugfix-firefox-class-in-computed-class-key, babel-traverse

🏠 Internal

Committers: 2

v7.25.2 (2024-07-30)

🐛 Bug Fix

... (truncated)

Changelog

Sourced from @​babel/preset-env's changelog.

v7.25.4 (2024-08-22)

🐛 Bug Fix

💅 Polish

  • babel-generator, babel-plugin-proposal-decorators, babel-plugin-proposal-destructuring-private, babel-plugin-proposal-pipeline-operator, babel-plugin-transform-class-properties, babel-plugin-transform-destructuring, babel-plugin-transform-optional-chaining, babel-plugin-transform-private-methods, babel-plugin-transform-private-property-in-object, babel-plugin-transform-typescript, babel-runtime-corejs2, babel-runtime, babel-traverse
  • babel-generator, babel-plugin-transform-class-properties
  • babel-generator, babel-plugin-proposal-decorators, babel-plugin-proposal-destructuring-private, babel-plugin-transform-object-rest-spread

🔬 Output optimization

v7.25.3 (2024-07-31)

🐛 Bug Fix

  • babel-plugin-bugfix-firefox-class-in-computed-class-key, babel-traverse

🏠 Internal

v7.25.2 (2024-07-30)

🐛 Bug Fix

v7.25.1 (2024-07-28)

🐛 Bug Fix

  • babel-plugin-transform-function-name
  • babel-plugin-transform-react-constant-elements
    • #16582 fix plugin-transform-react-constant-elements transform JSXFrament but not add JSXExpressionContainer (@​keiseiTi)
  • babel-traverse

🏠 Internal

Commits

Updates @types/node from 22.0.0 to 22.5.4

Commits

Updates @vscode/vsce from 2.31.1 to 3.1.0

Release notes

Sourced from @​vscode/vsce's releases.

v3.1.0

Changes:

Feature Requests:

  • #1044: Enable verifying the signed package

Others:

  • #1050: Fix unused-files-patterns check and add tests
  • #1046: Fix typo in option hint
  • #1045: add verify-signature command. Fixes #1044
  • #1037: Fix punycode deprecation warning
  • #1040: Allow packaging extension without a publisher

This list of changes was auto generated.

v3.0.1-4

Changes:

  • #1050: Fix unused-files-patterns check and add tests

This list of changes was auto generated.

v3.0.1-3

Changes:

  • #1046: Fix typo in option hint

This list of changes was auto generated.

v3.0.1-2

Changes:

Feature Requests:

  • #1044: Enable verifying the signed package

... (truncated)

Commits
  • ba66818 Merge pull request #1050 from microsoft/benibenj/narrow-smelt
  • 0e9cb5a More logging
  • 65f32a0 More error logging
  • a2e01db Merge branch 'main' into benibenj/narrow-smelt
  • 134eaa6 fix unused-files-patterns check and add tests
  • 3090717 Merge pull request #1046 from mlasson/patch-1
  • a583bab Fix typo in option hint
  • 164eebd add verify-signature command. Fixes #1044 (#1045)
  • e646982 Merge pull request #1037 from mark-wiemer/users/markwiemer/930-punycode
  • f7c7b44 Merge branch 'main' into users/markwiemer/930-punycode
  • Additional commits viewable in compare view

Updates concurrently from 8.2.2 to 9.0.0

Release notes

Sourced from concurrently's releases.

v9.0.0

💥 Breaking Changes

  • Dropped support for Node.js < 18.0.0. Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

  • The concurrently and default exports are now the same - #399 It's reasonable to expect that import { concurrently } from 'concurrently' would work the same as import concurrently from 'concurrently', however this has not been the case. The former used to be an unconfigured version of concurrently, lacking all features that you'd get from the CLI, which was seen as a "footgun". Both are now the same function.

    If you'd like to access the unconfigured function, use import { createConcurrently } from 'concurrently' instead.

✨ New Features

  • Exponential back-off support for process restarting - #265, #462 Use --restart-after exponential. Restarts happen at 2^N seconds.
  • Add prefix padding via new --pad-prefix flag - #166, #417, #495
  • Specify teardown commands via new --teardown flag - #472, #500
  • Expand node:<script> commands to node --run <script> - #475
  • [API only] Inter-Process Communication (ipc) - #498
  • [API only] Make it possible to use no colors at all - #466
  • [API only] Add a state field to Command - #455

🐛 Bug Fixes

  • Fix importing concurrently in ESM package - #454, #456, #494
  • Make sure concurrently doesn't resolve when manually restarting commands through API - #463, #464
  • Abort commands not running when max processes < N - #433, #452, #460
  • Fix warning coming from spawn-command when running in Node 22 - #407, #477, #479, #492
  • Make --raw and --hide compatible - #394, #486
  • Ensure prefix is written when logging without a trailing LF - #467

Other Changes

  • --help no longer shows examples due to there being too many. Refer to https://github.com/open-cli-tools/concurrently/tree/v9.0.0/docs instead, or to the node_modules/concurrently/docs directory in your project.
  • Improve examples of --passthrough-arguments - #490
  • Replace date-fns with hand-rolled date formatting - #436, #443 This should make installing concurrently faster.

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.2.2...v9.0.0

Commits
  • a7a5894 9.0.0
  • 758ee7f tests: update smoke tests lockfile
  • 710ee55 Replace date-fns for hand-rolled date formatting
  • fe7b69c deps: update @​types/node to 18.x.x too
  • fd2d140 Bump minimum Node version to 18
  • 37f98b2 deps: update several dev dependencies
  • 1b5df3a deps: update everything eslint
  • 7fc4803 Make it possible to use no colors at all through API
  • f4fb4f7 bin: fix SIGINT test on Windows
  • bd6ac58 bin: fix tests failing due to compilation to different dir
  • Additional commits viewable in compare view

Updates esbuild from 0.23.0 to 0.23.1

Release notes

Sourced from esbuild's releases.

v0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
    import fs from 'node:fs'
    fs.open
    // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
    import fs from "fs";
    fs.open;
    // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
    import fs from "node:fs";
    fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Changelog

Sourced from esbuild's changelog.

0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
    import fs from 'node:fs'
    fs.open
    // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
    import fs from "fs";
    fs.open;
    // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
    import fs from "node:fs";
    fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Commits

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the app-deps group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@babel/preset-env](https://github.com/babel/babel/tree/HEAD/packages/babel-preset-env) | `7.25.0` | `7.25.4` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `22.0.0` | `22.5.4` |
| [@vscode/vsce](https://github.com/Microsoft/vsce) | `2.31.1` | `3.1.0` |
| [concurrently](https://github.com/open-cli-tools/concurrently) | `8.2.2` | `9.0.0` |
| [esbuild](https://github.com/evanw/esbuild) | `0.23.0` | `0.23.1` |



Updates `@babel/preset-env` from 7.25.0 to 7.25.4
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.25.4/packages/babel-preset-env)

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

Updates `@vscode/vsce` from 2.31.1 to 3.1.0
- [Release notes](https://github.com/Microsoft/vsce/releases)
- [Commits](microsoft/vscode-vsce@v2.31.1...v3.1.0)

Updates `concurrently` from 8.2.2 to 9.0.0
- [Release notes](https://github.com/open-cli-tools/concurrently/releases)
- [Commits](open-cli-tools/concurrently@v8.2.2...v9.0.0)

Updates `esbuild` from 0.23.0 to 0.23.1
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.23.0...v0.23.1)

---
updated-dependencies:
- dependency-name: "@babel/preset-env"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: app-deps
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: app-deps
- dependency-name: "@vscode/vsce"
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: app-deps
- dependency-name: concurrently
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: app-deps
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: app-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 9, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Sep 16, 2024

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot bot closed this Sep 16, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/app-deps-73385da56e branch September 16, 2024 08:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants