build(deps): bump the babel group across 1 directory with 2 updates - #11546
build(deps): bump the babel group across 1 directory with 2 updates#11546dependabot[bot] wants to merge 1 commit into
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
2b73200 to
f3dd7b6
Compare
4f6e3a4 to
0eba31e
Compare
|
Hi @Dependabot (@dependabot)[bot]. Your PR has had no update for 14 days and it is marked as a stale PR. If it is not updated within 14 additional days, the PR will automatically be closed. If you want to refresh the PR, please remove the |
0eba31e to
5a7294b
Compare
There was a problem hiding this comment.
Pull request overview
This Dependabot PR updates the workspace dependency catalog and lockfile to move core Babel dependencies forward (notably @babel/code-frame and @babel/core) across the repo’s pnpm-managed packages.
Changes:
- Bumps
@babel/code-frameto^8.0.0and@babel/coreto^8.0.1in the pnpm catalog. - Regenerates
pnpm-lock.yamlto reflect the Babel 8 dependency graph and updated package metadata. - Updates the
packageExtensionsinjection for@alloy-js/rollup-plugin(but currently in a way that conflicts with the in-file rationale for keeping the Alloy toolchain on Babel 7).
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| pnpm-workspace.yaml | Updates catalog Babel versions and adjusts packageExtensions for the Alloy rollup plugin. |
| pnpm-lock.yaml | Updates resolved Babel versions/dependency tree and refreshes lock metadata (including a new deprecation notice). |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| "@alloy-js/rollup-plugin": | ||
| dependencies: | ||
| "@babel/core": ^7.29.0 | ||
| "@babel/core": ^8.0.1 |
| '@xmldom/xmldom@0.9.10': | ||
| resolution: {integrity: sha512-A9gOqLdi6cV4ibazAjcQufGj0B1y/vDqYrcuP6d/6x8P27gRS8643Dj9o1dEKtB6O7fwxb2FgBmJS2mX7gpvdw==} | ||
| engines: {node: '>=14.6'} | ||
| deprecated: this version has critical issues, please update to the latest version |
5a7294b to
3bcb991
Compare
3bcb991 to
b47ef0b
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
Suppressed comments (2)
pnpm-workspace.yaml:200
- The packageExtensions note says the Alloy rollup toolchain only supports Babel 7, but this PR changes the forced
@babel/coreversion to 8.0.1. That conflicts with @rollup/plugin-babel@7.1.0, which has a peerDependency on@babel/core^7.0.0 (pnpm-lock.yaml:5765-5767), and results in mixed Babel 7/8 variants in the lockfile (pnpm-lock.yaml:11229-11234). Keep@babel/corepinned to a 7.x range for@alloy-js/rollup-pluginunless the whole toolchain is upgraded to Babel 8-compatible versions.
"@alloy-js/rollup-plugin":
dependencies:
"@babel/core": ^8.0.1
pnpm-lock.yaml:6578
- pnpm-lock now records @xmldom/xmldom@0.9.10 as deprecated due to “critical issues”. Since this dependency comes in via plist@5.0.0 (pnpm-lock.yaml:19054-19057), it would be good to follow up by bumping plist and/or adding an override to move off the deprecated xmldom version.
b47ef0b to
7496fad
Compare
7496fad to
c9f4b87
Compare
Bumps the babel group with 2 updates in the / directory: [@babel/code-frame](https://github.com/babel/babel/tree/HEAD/packages/babel-code-frame) and [@babel/core](https://github.com/babel/babel/tree/HEAD/packages/babel-core). Updates `@babel/code-frame` from 7.12.11 to 8.0.0 - [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/v8.0.0/packages/babel-code-frame) Updates `@babel/core` from 7.29.7 to 8.0.1 - [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/v8.0.1/packages/babel-core) --- updated-dependencies: - dependency-name: "@babel/code-frame" dependency-version: 8.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: babel - dependency-name: "@babel/core" dependency-version: 8.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: babel ... Signed-off-by: dependabot[bot] <support@github.com>
c9f4b87 to
b414420
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
Suppressed comments (1)
pnpm-workspace.yaml:200
- The
packageExtensionsblock comments that@alloy-js/rollup-plugin -> @babel/preset-typescript@7.xonly supports Babel 7 and that adding an explicit@babel/coredependency is meant to keep the toolchain on Babel 7. Updating this to^8.0.1contradicts that and will likely reintroduce the Babel 7 peer mismatch.
# "Requires Babel ^7.0.0-0". Give the plugin an explicit @babel/core dependency so the whole
# toolchain resolves against Babel 7.
"@alloy-js/rollup-plugin":
dependencies:
"@babel/core": ^8.0.1
| '@alloy-js/rollup-plugin@0.1.2(@types/babel__core@7.20.5)': | ||
| dependencies: | ||
| '@alloy-js/babel-preset': 0.3.0(@babel/core@7.29.7) | ||
| '@babel/core': 7.29.7 | ||
| '@alloy-js/babel-preset': 0.3.0(@babel/core@8.0.1) | ||
| '@babel/core': 8.0.1 | ||
| '@babel/preset-typescript': 7.29.7(@babel/core@7.29.7) | ||
| '@rollup/plugin-babel': 7.1.0(@babel/core@7.29.7)(@types/babel__core@7.20.5) |
| "@azure/storage-blob": ^12.31.0 | ||
| "@babel/code-frame": ^7.29.0 | ||
| "@babel/core": ^7.29.0 | ||
| "@babel/code-frame": ^8.0.0 | ||
| "@babel/core": ^8.0.1 |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
Suppressed comments (3)
pnpm-workspace.yaml:200
- The packageExtensions block documents pinning the
@alloy-js/rollup-plugintoolchain to Babel 7 (because @babel/preset-typescript@7.x has peerDependency @babel/core:^7), but this sets@babel/coreto ^8.0.1. That defeats the purpose of this extension and can reintroduce the Babel 7 peer mismatch for the rollup toolchain.
"@babel/core": ^8.0.1
pnpm-lock.yaml:11234
- The lockfile shows
@alloy-js/rollup-pluginresolving to @babel/core@8.0.1 while still pulling @babel/preset-typescript@7.29.7 (which peers on @babel/core:^7.0.0-0) and@rollup/plugin-babelpinned to @babel/core@7.29.7. Mixing Babel major versions in the same toolchain is likely to break builds; either keep the toolchain on Babel 7 or upgrade the preset/plugin chain to Babel 8 compatible versions and regenerate the lockfile.
pnpm-lock.yaml:6578 - The lockfile indicates @xmldom/xmldom@0.9.10 is deprecated due to "critical issues". Even though it is likely transitive, this is a security risk worth addressing by updating the dependency chain to a non-deprecated version.
| '@babel/code-frame@8.0.0': | ||
| resolution: {integrity: sha512-dYYg153EyN2Ekbqw2zAsbd6/JR+9N2SEoC7YV2GyyqMM7x9bLDTjBD6XBhSMLH0wtIVyJj03jWNriQhaN+eoCw==} | ||
| engines: {node: ^22.18.0 || >=24.11.0} | ||
|
|
||
| '@babel/compat-data@7.29.7': | ||
| resolution: {integrity: sha512-locTkQyKvwIEgBzVrn8693ebc97F2U8ZHjbXwDXJ5Fn2TCpNwTlKcaKLkdHop5c/icOFE7qt7Q9JC5hnKNa6Gg==} | ||
| engines: {node: '>=6.9.0'} | ||
|
|
||
| '@babel/compat-data@8.0.0': | ||
| resolution: {integrity: sha512-DOjnob/cXOUgDOozCDeq/aK2p5y8dUIVdf6tNhEV1HQRd6I8aQ4f4fbtHRVEvb6lP3BGomrKHiS8ICAASSVQSw==} | ||
| engines: {node: ^22.18.0 || >=24.11.0} | ||
|
|
||
| '@babel/core@7.29.7': | ||
| resolution: {integrity: sha512-RgHBCvtjbOK2gXSNBNIkNoEc9qoVEtau3hj8gEqKQuL3HZAibKarWFEI3Lfm6EYKkLalOh8eSrj9b+ch9H/VBA==} | ||
| engines: {node: '>=6.9.0'} | ||
|
|
||
| '@babel/core@8.0.1': | ||
| resolution: {integrity: sha512-5FgxM4dLQpMJHSiVATk8foW263dVHQHBVpXYiimNECVWG01f4nFyEbQixeT6Mwvg7TayREJ2gpKl3o2RoMdnqw==} | ||
| engines: {node: ^22.18.0 || >=24.11.0} | ||
|
|
Bumps the babel group with 2 updates in the / directory: @babel/code-frame and @babel/core.
Updates
@babel/code-framefrom 7.12.11 to 8.0.0Release notes
Sourced from @babel/code-frame's releases.
... (truncated)
Changelog
Sourced from @babel/code-frame's changelog.
... (truncated)
Commits
7dc825av8.0.073bceefv8.0.0-rc.6dc91f90v8.0.0-rc.5e77fa07breaking(code-frame): use 0-based columns to match Babel AST locations (#1… (...7f2dda1chore: add custom no-extraneous-dependencies rule (#17971)0e5a59dRequire Node.js^22.18.0 || >=24.11.0(#17969)7300a66v8.0.0-rc.4c1cc900v8.0.0-rc.34fcbae7EnablestrictNullChecksfor more packages (#17828)407be40v8.0.0-rc.2Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@babel/code-framesince your current version.Updates
@babel/corefrom 7.29.7 to 8.0.1Release notes
Sourced from @babel/core's releases.
... (truncated)
Changelog
Sourced from @babel/core's changelog.
... (truncated)
Commits
b4be199v8.0.1b68b1cbActually removepreset-env'suseBuiltIns(#18079)de007eaAvoid trailing zeroes in Babel 9 generated version (#18078)7dc825av8.0.0b71c35aperf: Only extract source map comments at the end of the file (#18039)e74b70dchore: Remove unused file (#18033)ae57969chore: consolidate upwards traversal to empathic (#18030)827d003Change jestsnapshotFormat(#18029)34cf24eUpdate deps (#18023)73bceefv8.0.0-rc.6