deps: bump the dependency-updates group with 14 updates
Type: Pull Request
State: Open
Association: None
Comments: 1
(3 months ago)
(3 months ago)
dependencies
Bumps the dependency-updates group with 14 updates:
| Package | From | To |
|---|---|---|
| @mdx-js/mdx | 3.1.0 |
3.1.1 |
| @mdx-js/react | 3.1.0 |
3.1.1 |
| @primer/octicons-react | 19.15.5 |
19.16.0 |
| gatsby | 5.14.6 |
5.15.0 |
| gatsby-plugin-manifest | 5.14.0 |
5.15.0 |
| gatsby-plugin-mdx | 5.14.1 |
5.15.0 |
| gatsby-plugin-postcss | 6.14.0 |
6.15.0 |
| gatsby-plugin-styled-components | 6.14.0 |
6.15.0 |
| gatsby-source-filesystem | 5.14.0 |
5.15.0 |
| gatsby-transformer-yaml | 5.14.0 |
5.15.0 |
| postcss-preset-env | 10.3.0 |
10.3.1 |
| babel-jest | 30.0.5 |
30.1.1 |
| jest | 30.0.5 |
30.1.1 |
| jest-environment-jsdom | 30.0.5 |
30.1.1 |
Updates @mdx-js/mdx from 3.1.0 to 3.1.1
Release notes
Sourced from @mdx-js/mdx's releases.
3.1.1
Fix
- 3cad7d7e
@mdx-js/mdx: add dependency onacorn- 0dc4472f
@mdx-js/esbuild: fix crash with esbuild loader andjsxoption by@egnorin mdx-js/mdx#2593- 84ec66ef
@mdx-js/esbuild: refactor to improve error conversion in esbuild by@egnorin mdx-js/mdx#2595- 2b3381a8
@mdx-js/rollup: fix support for query parameters in Vite by@markdalgleishin mdx-js/mdx#2629Types
- 933ab444
@mdx-js/mdx: addattributesto export/import declarationsDocs
- c156a1f6 Add
rehype-mdx-tocto list of plugin by@boning-win mdx-js/mdx#2622- 913659c8 Add
recma-module-to-functionto list of plugins by@remcohaszingin mdx-js/mdx#2605- 67fb1d07 Remove unneeded JSX type casting in docs, tests
- f0d20da8 Remove local use of
JSXby@remcohaszingin mdx-js/mdx#2604- 63f39cea Remove references to twitter
- 35ac59dd Refactor some docs regarding recma plugins
Full Changelog: https://github.com/mdx-js/mdx/compare/3.1.0...3.1.1
Commits
Updates @mdx-js/react from 3.1.0 to 3.1.1
Release notes
Sourced from @mdx-js/react's releases.
3.1.1
Fix
- 3cad7d7e
@mdx-js/mdx: add dependency onacorn- 0dc4472f
@mdx-js/esbuild: fix crash with esbuild loader andjsxoption by@egnorin mdx-js/mdx#2593- 84ec66ef
@mdx-js/esbuild: refactor to improve error conversion in esbuild by@egnorin mdx-js/mdx#2595- 2b3381a8
@mdx-js/rollup: fix support for query parameters in Vite by@markdalgleishin mdx-js/mdx#2629Types
- 933ab444
@mdx-js/mdx: addattributesto export/import declarationsDocs
- c156a1f6 Add
rehype-mdx-tocto list of plugin by@boning-win mdx-js/mdx#2622- 913659c8 Add
recma-module-to-functionto list of plugins by@remcohaszingin mdx-js/mdx#2605- 67fb1d07 Remove unneeded JSX type casting in docs, tests
- f0d20da8 Remove local use of
JSXby@remcohaszingin mdx-js/mdx#2604- 63f39cea Remove references to twitter
- 35ac59dd Refactor some docs regarding recma plugins
Full Changelog: https://github.com/mdx-js/mdx/compare/3.1.0...3.1.1
Commits
50aa8df3.1.167fb1d0Remove unneeded JSX type casting in docs, testsf0d20daRemove local use ofJSXe587c8cUpdateremark-preset-wooorm- See full diff in compare view
Updates @primer/octicons-react from 19.15.5 to 19.16.0
Release notes
Sourced from @primer/octicons-react's releases.
v19.16.0
Minor Changes
- #1107
4073a521Thanks@CameronFoxly! - Add minimize-16.svg, maximize-16.svg, maximize-24.svg, minimize-24.svgPatch Changes
- #1112
36fd097fThanks@lukasoppermann! - Adjusted alignment of repo delete, locked and push icon in 16px and 24px
Changelog
Sourced from @primer/octicons-react's changelog.
19.16.0
Minor Changes
- #1107
4073a521Thanks@CameronFoxly! - Add minimize-16.svg, maximize-16.svg, maximize-24.svg, minimize-24.svgPatch Changes
- #1112
36fd097fThanks@lukasoppermann! - Adjusted alignment of repo delete, locked and push icon in 16px and 24px
Commits
52369b2Version Packages (#1108)36fd097Adjusted alignment of repo delete, locked and push icon in 16 and 24px (#1112)50d83e5Bump braces from 2.3.1 to 3.0.3 (#1106)31f28cbBump sha.js from 2.4.11 to 2.4.12 in /lib/octicons_styled (#1109)4073a52Add minimize-16.svg, maximize-16.svg, maximize-24.svg, minimize-24.svg (#1107)0a5cc76Bump next from 14.2.26 to 14.2.30 in /lib/octicons_react (#1094)ff730e8Bump pbkdf2 from 3.1.2 to 3.1.3 in /lib/octicons_styled (#1095)- See full diff in compare view
Updates gatsby from 5.14.6 to 5.15.0
Release notes
Sourced from gatsby's releases.
gatsby@5.15.0
What's Changed
- fix: support node 22 by
@serhalpin gatsbyjs/gatsby#39349- fix(gatsby): update socket.io to address vulnerable subdeps by
@serhalpin gatsbyjs/gatsby#39352Node.js 22
This release formally introduces Node.js 22 support, which is officially tested and supported going forward.
If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.
⚠️ Known Issue:
gatsby developfails with Node.js 22.7.0, 22.8.0, and 22.9.0There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes
gatsby developto fail with the error reported in gatsbyjs/gatsby#39068.👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)
⚠️ Known Issue: Page loads may hang in dev with experimental
DEV_SSRenabled and Node.js ≥22.14.0 (or ≥20.19.0)This will not affect most users.
A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the
gatsby developdev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimentalDEV_SSRflag.👉🏼 To avoid this, disable the experimental
DEV_SSRflag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)New Contributors
Thank you!
@pajosiegmade their first contribution in gatsbyjs/gatsby#39169@johnmurphy01made their first contribution in gatsbyjs/gatsby#39324@shrisoundharyaamade their first contribution in gatsbyjs/gatsby#39286Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0
Commits
e3d0717chore(release): Publish7451d2ffix: support node 22 (#39349)c3708b0chore: remove Gatsby Discord references (#39351)6ba3b68fix(gatsby): update socket.io to address vulnerable subdeps (#39352)19a8015chore(renovate): remove invalid optionf732190chore: simplify Renovate setup (#39339)1711f91chore: relocate deprecated packages (#39350)647ea2cci: improve parallelisation of jobs (#39354)d3ec326fix(deps): update starters and examples - gatsby (#39267)79a8689chore(changelogs): update changelogs (#39346)- Additional commits viewable in compare view
Updates gatsby-plugin-manifest from 5.14.0 to 5.15.0
Release notes
Sourced from gatsby-plugin-manifest's releases.
gatsby@5.15.0
What's Changed
- fix: support node 22 by
@serhalpin gatsbyjs/gatsby#39349- fix(gatsby): update socket.io to address vulnerable subdeps by
@serhalpin gatsbyjs/gatsby#39352Node.js 22
This release formally introduces Node.js 22 support, which is officially tested and supported going forward.
If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.
⚠️ Known Issue:
gatsby developfails with Node.js 22.7.0, 22.8.0, and 22.9.0There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes
gatsby developto fail with the error reported in gatsbyjs/gatsby#39068.👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)
⚠️ Known Issue: Page loads may hang in dev with experimental
DEV_SSRenabled and Node.js ≥22.14.0 (or ≥20.19.0)This will not affect most users.
A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the
gatsby developdev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimentalDEV_SSRflag.👉🏼 To avoid this, disable the experimental
DEV_SSRflag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)New Contributors
Thank you!
@pajosiegmade their first contribution in gatsbyjs/gatsby#39169@johnmurphy01made their first contribution in gatsbyjs/gatsby#39324@shrisoundharyaamade their first contribution in gatsbyjs/gatsby#39286Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0
gatsby@5.14.6
2025-08-06
What's Changed
- fix: don't treat timestamps as dynamic paths (#39340) by
@gatsbybotin gatsbyjs/gatsby#39341- fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by
@gatsbybotin gatsbyjs/gatsby#39345
- This fixes npm install errors/warnings with Node.js 18 that look like
error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6
gatsby@5.14.5
2025-06-19
... (truncated)
Changelog
Sourced from gatsby-plugin-manifest's changelog.
5.15.0 (2025-08-27)
Note: Version bump only for package gatsby-plugin-manifest
Commits
e3d0717chore(release): Publish17baffbchore(release): Publish next pre-minor5f44fcdchore(changelogs): update changelogs (#39156)- See full diff in compare view
Updates gatsby-plugin-mdx from 5.14.1 to 5.15.0
Release notes
Sourced from gatsby-plugin-mdx's releases.
gatsby@5.15.0
What's Changed
- fix: support node 22 by
@serhalpin gatsbyjs/gatsby#39349- fix(gatsby): update socket.io to address vulnerable subdeps by
@serhalpin gatsbyjs/gatsby#39352Node.js 22
This release formally introduces Node.js 22 support, which is officially tested and supported going forward.
If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.
⚠️ Known Issue:
gatsby developfails with Node.js 22.7.0, 22.8.0, and 22.9.0There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes
gatsby developto fail with the error reported in gatsbyjs/gatsby#39068.👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)
⚠️ Known Issue: Page loads may hang in dev with experimental
DEV_SSRenabled and Node.js ≥22.14.0 (or ≥20.19.0)This will not affect most users.
A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the
gatsby developdev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimentalDEV_SSRflag.👉🏼 To avoid this, disable the experimental
DEV_SSRflag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)New Contributors
Thank you!
@pajosiegmade their first contribution in gatsbyjs/gatsby#39169@johnmurphy01made their first contribution in gatsbyjs/gatsby#39324@shrisoundharyaamade their first contribution in gatsbyjs/gatsby#39286Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0
gatsby@5.14.6
2025-08-06
What's Changed
- fix: don't treat timestamps as dynamic paths (#39340) by
@gatsbybotin gatsbyjs/gatsby#39341- fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by
@gatsbybotin gatsbyjs/gatsby#39345
- This fixes npm install errors/warnings with Node.js 18 that look like
error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6
gatsby@5.14.5
2025-06-19
... (truncated)
Commits
Updates gatsby-plugin-postcss from 6.14.0 to 6.15.0
Release notes
Sourced from gatsby-plugin-postcss's releases.
gatsby-source-wordpress@7.13.5 and 6 more...
2024-08-26
Updated packages
- gatsby-source-wordpress@7.13.5
- gatsby-remark-responsive-iframe@6.13.2
- gatsby-remark-prismjs@7.13.2
- gatsby-remark-images@7.13.2
- gatsby-remark-images@6.13.2
- gatsby-remark-graphviz@5.13.2
- gatsby-remark-copy-linked-files@6.13.2
- gatsby-plugin-offline@6.13.3
What's Changed
- fix: pin cheerio (#39066) by
@gatsbybotin gatsbyjs/gatsby#39069See full release notes: gatsbyjs/gatsby#39070
Changelog
Sourced from gatsby-plugin-postcss's changelog.
6.15.0 (2025-08-27)
Note: Version bump only for package gatsby-plugin-postcss
Commits
e3d0717chore(release): Publish17baffbchore(release): Publish next pre-minor5f44fcdchore(changelogs): update changelogs (#39156)- See full diff in compare view
Updates gatsby-plugin-styled-components from 6.14.0 to 6.15.0
Release notes
Sourced from gatsby-plugin-styled-components's releases.
gatsby-source-wordpress@7.13.5 and 6 more...
2024-08-26
Updated packages
- gatsby-source-wordpress@7.13.5
- gatsby-remark-responsive-iframe@6.13.2
- gatsby-remark-prismjs@7.13.2
- gatsby-remark-images@7.13.2
- gatsby-remark-images@6.13.2
- gatsby-remark-graphviz@5.13.2
- gatsby-remark-copy-linked-files@6.13.2
- gatsby-plugin-offline@6.13.3
What's Changed
- fix: pin cheerio (#39066) by
@gatsbybotin gatsbyjs/gatsby#39069See full release notes: gatsbyjs/gatsby#39070
Changelog
Sourced from gatsby-plugin-styled-components's changelog.
6.15.0 (2025-08-27)
Note: Version bump only for package gatsby-plugin-styled-components
Commits
e3d0717chore(release): Publish17baffbchore(release): Publish next pre-minor5f44fcdchore(changelogs): update changelogs (#39156)- See full diff in compare view
Updates gatsby-source-filesystem from 5.14.0 to 5.15.0
Release notes
Sourced from gatsby-source-filesystem's releases.
gatsby@5.15.0
What's Changed
- fix: support node 22 by
@serhalpin gatsbyjs/gatsby#39349- fix(gatsby): update socket.io to address vulnerable subdeps by
@serhalpin gatsbyjs/gatsby#39352Node.js 22
This release formally introduces Node.js 22 support, which is officially tested and supported going forward.
If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.
⚠️ Known Issue:
gatsby developfails with Node.js 22.7.0, 22.8.0, and 22.9.0There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes
gatsby developto fail with the error reported in gatsbyjs/gatsby#39068.👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)
⚠️ Known Issue: Page loads may hang in dev with experimental
DEV_SSRenabled and Node.js ≥22.14.0 (or ≥20.19.0)This will not affect most users.
A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the
gatsby developdev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimentalDEV_SSRflag.👉🏼 To avoid this, disable the experimental
DEV_SSRflag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)New Contributors
Thank you!
@pajosiegmade their first contribution in gatsbyjs/gatsby#39169@johnmurphy01made their first contribution in gatsbyjs/gatsby#39324@shrisoundharyaamade their first contribution in gatsbyjs/gatsby#39286Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0
gatsby@5.14.6
2025-08-06
What's Changed
- fix: don't treat timestamps as dynamic paths (#39340) by
@gatsbybotin gatsbyjs/gatsby#39341- fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by
@gatsbybotin gatsbyjs/gatsby#39345
- This fixes npm install errors/warnings with Node.js 18 that look like
error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6
gatsby@5.14.5
2025-06-19
... (truncated)
Commits
Updates gatsby-transformer-yaml from 5.14.0 to 5.15.0
Release notes
Sourced from gatsby-transformer-yaml's releases.
gatsby@5.15.0
What's Changed
- fix: support node 22 by
@serhalpin gatsbyjs/gatsby#39349- fix(gatsby): update socket.io to address vulnerable subdeps by
@serhalpin gatsbyjs/gatsby#39352Node.js 22
This release formally introduces Node.js 22 support, which is officially tested and supported going forward.
If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.
⚠️ Known Issue:
gatsby developfails with Node.js 22.7.0, 22.8.0, and 22.9.0There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes
gatsby developto fail with the error reported in gatsbyjs/gatsby#39068.👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)
⚠️ Known Issue: Page loads may hang in dev with experimental
DEV_SSRenabled and Node.js ≥22.14.0 (or ≥20.19.0)This will not affect most users.
A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the
gatsby developdev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimentalDEV_SSRflag.👉🏼 To avoid this, disable the experimental
DEV_SSRflag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)New Contributors
Thank you!
@pajosiegmade their first contribution in gatsbyjs/gatsby#39169@johnmurphy01made their first contribution in gatsbyjs/gatsby#39324@shrisoundharyaamade their first contribution in gatsbyjs/gatsby#39286Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0
gatsby@5.14.6
2025-08-06
What's Changed
- fix: don't treat timestamps as dynamic paths (#39340) by
@gatsbybotin gatsbyjs/gatsby#39341- fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by
@gatsbybotin gatsbyjs/gatsby#39345
- This fixes npm install errors/warnings with Node.js 18 that look like
error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6
gatsby@5.14.5
2025-06-19
... (truncated)
Changelog
Sourced from gatsby-transformer-yaml's changelog.
5.15.0 (2025-08-27)
Note: Version bump only for package gatsby-transformer-yaml
Commits
e3d0717chore(release): Publish17baffbchore(release): Publish next pre-minor5f44fcdchore(changelogs): update changelogs (#39156)- See full diff in compare view
Updates postcss-preset-env from 10.3.0 to 10.3.1
Changelog
Sourced from postcss-preset-env's changelog.
10.3.1
August 27, 2025
- Updated
css-has-pseudoto7.0.3(patch)
Commits
- See full diff in compare view
Updates babel-jest from 30.0.5 to 30.1.1
Release notes
Sourced from babel-jest's releases.
30.1.1
Fixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#15800)30.1.0
Features
[jest-leak-detector]Configurable GC aggressiveness regarding to V8 heap snapshot generation (#15793)[jest-runtime]Reduce redundant ReferenceError messages[jest-core]Include test modules that failed to load when --onlyFailures is activeFixes
- `[jest-snapshot-utils] Fix deprecated goo.gl snapshot guide link not getting replaced with fully canonical URL (#15787)
[jest-circus]Fixit.concurrentnot working withdescribe.skip(#15765)[jest-snapshot]Fix mangled inline snapshot updates when used with Prettier 3 and CRLF line endings[jest-runtime]Importing from@jest/globalsin more than one file no longer breaks relative paths (#15772)Chore
[expect]Update docblock fortoContain()to display info on substring check (#15789)
Changelog
Sourced from babel-jest's changelog.
30.1.1
Fixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#15800)30.1.0
Features
[jest-leak-detector]Configurable GC aggressiveness regarding to V8 heap snapshot generation (#15793)[jest-runtime]Reduce redundant ReferenceError messages[jest-core]Include test modules that failed to load when --onlyFailures is activeFixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot guide link not getting replaced with fully canonical URL (#15787)[jest-circus]Fixit.concurrentnot working withdescribe.skip(#15765)[jest-snapshot]Fix mangled inline snapshot updates when used with Prettier 3 and CRLF line endings[jest-runtime]Importing from@jest/globalsin more than one file no longer breaks relative paths (#15772)Chore
[expect]Update docblock fortoContain()to display info on substring check (#15789)
Commits
d347c0fv30.1.14d5f41dv30.1.0- See full diff in compare view
Updates jest from 30.0.5 to 30.1.1
Release notes
Sourced from jest's releases.
30.1.1
Fixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#15800)30.1.0
Features
[jest-leak-detector]Configurable GC aggressiveness regarding to V8 heap snapshot generation (#15793)[jest-runtime]Reduce redundant ReferenceError messages[jest-core]Include test modules that failed to load when --onlyFailures is activeFixes
- `[jest-snapshot-utils] Fix deprecated goo.gl snapshot guide link not getting replaced with fully canonical URL (#15787)
[jest-circus]Fixit.concurrentnot working withdescribe.skip(#15765)[jest-snapshot]Fix mangled inline snapshot updates when used with Prettier 3 and CRLF line endings[jest-runtime]Importing from@jest/globalsin more than one file no longer breaks relative paths (#15772)Chore
[expect]Update docblock fortoContain()to display info on substring check (#15789)
Changelog
Sourced from jest's changelog.
30.1.1
Fixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#15800)30.1.0
Features
[jest-leak-detector]Configurable GC aggressiveness regarding to V8 heap snapshot generation (#15793)[jest-runtime]Reduce redundant ReferenceError messages[jest-core]Include test modules that failed to load when --onlyFailures is activeFixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot guide link not getting replaced with fully canonical URL (#15787)[jest-circus]Fixit.concurrentnot working withdescribe.skip(#15765)[jest-snapshot]Fix mangled inline snapshot updates when used with Prettier 3 and CRLF line endings[jest-runtime]Importing from@jest/globalsin more than one file no longer breaks relative paths (#15772)Chore
[expect]Update docblock fortoContain()to display info on substring check (#15789)
Commits
d347c0fv30.1.14d5f41dv30.1.0- See full diff in compare view
Updates jest-environment-jsdom from 30.0.5 to 30.1.1
Release notes
Sourced from jest-environment-jsdom's releases.
30.1.1
Fixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#15800)30.1.0
Features
[jest-leak-detector]Configurable GC aggressiveness regarding to V8 heap snapshot generation (#15793)[jest-runtime]Reduce redundant ReferenceError messages[jest-core]Include test modules that failed to load when --onlyFailures is activeFixes
- `[jest-snapshot-utils] Fix deprecated goo.gl snapshot guide link not getting replaced with fully canonical URL (#15787)
[jest-circus]Fixit.concurrentnot working withdescribe.skip(#15765)[jest-snapshot]Fix mangled inline snapshot updates when used with Prettier 3 and CRLF line endings[jest-runtime]Importing from@jest/globalsin more than one file no longer breaks relative paths (#15772)Chore
[expect]Update docblock fortoContain()to display info on substring check (#15789)
Changelog
Sourced from jest-environment-jsdom's changelog.
30.1.1
Fixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#15800)30.1.0
Features
[jest-leak-detector]Configurable GC aggressiveness regarding to V8 heap snapshot generation (#15793)[jest-runtime]Reduce redundant ReferenceError messages[jest-core]Include test modules that failed to load when --onlyFailures is activeFixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot guide link not getting replaced with fully canonical URL (#15787)[jest-circus]Fixit.concurrentnot working withdescribe.skip(#15765)[jest-snapshot]Fix mangled inline snapshot updates when used with Prettier 3 and CRLF line endings[jest-runtime]Importing from@jest/globalsin more than one file no longer breaks relative paths (#15772)Chore
[expect]Update docblock fortoContain()to display info on substring check (#15789)
Commits
d347c0fv30.1.14d5f41dv30.1.0- See full diff in compare view
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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
Pull Request Statistics
0
0
+0
-0
Package Dependencies
gatsby-plugin-styled-components
npm
6.14.0 → 6.15.0
Minor
Technical Details
| ID: | 6451380 |
| UUID: | 3370699290 |
| Node ID: | PR_kwDOPnhU4M6mLqiE |
| Host: | GitHub |
| Repository: | DM-enterprises/docs.npmjs.com- |