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

chore(deps): bump json5, gatsby, gatsby-plugin-manifest, gatsby-plugin-mdx, webpack and gatsby-plugin-sass #361

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

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jan 2, 2023

Bumps json5 to 2.2.3 and updates ancestor dependencies json5, gatsby, gatsby-plugin-manifest, gatsby-plugin-mdx, webpack and gatsby-plugin-sass. These dependencies need to be updated together.

Updates json5 from 2.2.0 to 2.2.3

Release notes

Sourced from json5's releases.

v2.2.3

v2.2.2

  • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

v2.2.1

Changelog

Sourced from json5's changelog.

v2.2.3 [code, diff]

v2.2.2 [code, diff]

  • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

v2.2.1 [code, diff]

Commits
  • c3a7524 2.2.3
  • 94fd06d docs: update CHANGELOG for v2.2.3
  • 3b8cebf docs(security): use GitHub security advisories
  • f0fd9e1 docs: publish a security policy
  • 6a91a05 docs(template): bug -> bug report
  • 14f8cb1 2.2.2
  • 10cc7ca docs: update CHANGELOG for v2.2.2
  • 7774c10 fix: add proto to objects and arrays
  • edde30a Readme: slight tweak to intro
  • 97286f8 Improve example in readme
  • Additional commits viewable in compare view

Updates gatsby from 2.32.13 to 5.3.3

Release notes

Sourced from gatsby's releases.

v5.3.0

Welcome to [email protected] release (December 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.2.0

Welcome to [email protected] release (November 2022 #3)

This is an out of band release due to the removal of the Potrace library in Gatsby. We'll continue with our biweekly schedule as normal.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.1.0

Welcome to [email protected] release (November 2022 #2)

This is the first minor release after the recent major release of Gatsby 5! We are focused on your feedback and implementing fixes as needed.

If you haven’t migrated yet, please refer to the migration guide. We’ve done our best to make the transition smooth!

Some brief notes about what Gatsby 5 brings to the table:

  • Slices API unlocks up to 90% reduction in build duration for content changes in highly shared components
  • Partial Hydration allows you to ship only the necessary JavaScript to the browser

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.0.0

Welcome to [email protected] release (November 2022 #1)

Key highlights of this release:

Major dependency updates:

... (truncated)

Commits
  • da692c7 chore(release): Publish
  • e333019 fix(gatsby-transformer-remark): Disallow JS frontmatter by default (#37244) (...
  • 3e7e996 fix(gatsby): [rendering engines] use results of exports removal if sourceMap ...
  • f448e12 fix(gatsby): don't output file-loader assets to .cache (#37284) (#37295)
  • 8fc123c chore(release): Publish
  • b7477f4 fix(gatsby-plugin-image): Normalize filename for correct hashing (#37262) (#3...
  • 98cbee1 chore(release): Publish
  • a283319 fix(gatsby): use file:// protocol when importing gatsby-config/node (#37257) ...
  • 287cabd chore(release): Publish
  • e9aafe4 Revert "fix(deps): update dependency lmdb to v2.7.1 (#37160)" (#37255) (#37258)
  • Additional commits viewable in compare view

Updates gatsby-plugin-manifest from 2.12.1 to 5.3.1

Release notes

Sourced from gatsby-plugin-manifest's releases.

v5.3.0

Welcome to [email protected] release (December 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.2.0

Welcome to [email protected] release (November 2022 #3)

This is an out of band release due to the removal of the Potrace library in Gatsby. We'll continue with our biweekly schedule as normal.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.1.0

Welcome to [email protected] release (November 2022 #2)

This is the first minor release after the recent major release of Gatsby 5! We are focused on your feedback and implementing fixes as needed.

If you haven’t migrated yet, please refer to the migration guide. We’ve done our best to make the transition smooth!

Some brief notes about what Gatsby 5 brings to the table:

  • Slices API unlocks up to 90% reduction in build duration for content changes in highly shared components
  • Partial Hydration allows you to ship only the necessary JavaScript to the browser

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.0.0

Welcome to [email protected] release (November 2022 #1)

Key highlights of this release:

Major dependency updates:

... (truncated)

Changelog

Sourced from gatsby-plugin-manifest's changelog.

5.3.1 (2022-12-14)

Note: Version bump only for package gatsby-plugin-manifest

5.3.0 (2022-12-13)

🧾 Release notes

Chores

5.2.0 (2022-11-25)

🧾 Release notes

Other Changes

5.1.0 (2022-11-22)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-manifest

5.0.0 (2022-11-08)

🧾 Release notes

Chores

4.24.0 (2022-09-27)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-manifest

4.23.1 (2022-09-22)

Note: Version bump only for package gatsby-plugin-manifest

4.23.0 (2022-09-13)

🧾 Release notes

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by marvinjudehk, a new releaser for gatsby-plugin-manifest since your current version.


Updates gatsby-plugin-mdx from 1.10.1 to 5.3.1

Release notes

Sourced from gatsby-plugin-mdx's releases.

v5.3.0

Welcome to [email protected] release (December 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.2.0

Welcome to [email protected] release (November 2022 #3)

This is an out of band release due to the removal of the Potrace library in Gatsby. We'll continue with our biweekly schedule as normal.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.1.0

Welcome to [email protected] release (November 2022 #2)

This is the first minor release after the recent major release of Gatsby 5! We are focused on your feedback and implementing fixes as needed.

If you haven’t migrated yet, please refer to the migration guide. We’ve done our best to make the transition smooth!

Some brief notes about what Gatsby 5 brings to the table:

  • Slices API unlocks up to 90% reduction in build duration for content changes in highly shared components
  • Partial Hydration allows you to ship only the necessary JavaScript to the browser

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.0.0

Welcome to [email protected] release (November 2022 #1)

Key highlights of this release:

Major dependency updates:

... (truncated)

Changelog

Sourced from gatsby-plugin-mdx's changelog.

5.3.1 (2022-12-14)

Note: Version bump only for package gatsby-plugin-mdx

5.3.0 (2022-12-13)

🧾 Release notes

Bug Fixes

  • update minor and patch dependencies for gatsby-plugin-mdx #37154 (0d40674)

Chores

5.2.0 (2022-11-25)

🧾 Release notes

Chores

5.1.0 (2022-11-22)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-mdx

5.0.0 (2022-11-08)

🧾 Release notes

Bug Fixes

Chores

4.3.0 (2022-09-27)

🧾 Release notes

... (truncated)

Commits
  • 287cabd chore(release): Publish
  • b995fc2 chore(release): Publish
  • 03d6c59 chore(release): Publish next
  • 204ed0e chore(deps): update dependency typescript to ^4.9.3 (#37192)
  • 1dc347c chore(release): Publish next
  • 5a8879c chore(deps): update formatting & linting (#37159)
  • 0d40674 fix(deps): update minor and patch dependencies for gatsby-plugin-mdx (#37154)
  • 11efd36 chore(release): Publish next
  • 30c8c61 chore(changelogs): update changelogs (#37106)
  • 7c27b0d chore(release): Publish next pre-minor
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by marvinjudehk, a new releaser for gatsby-plugin-mdx since your current version.


Updates webpack from 4.46.0 to 5.75.0

Release notes

Sourced from webpack's releases.

v5.75.0

Bugfixes

  • experiments.* normalize to false when opt-out
  • avoid NaN%
  • show the correct error when using a conflicting chunk name in code
  • HMR code tests existance of window before trying to access it
  • fix eval-nosources-* actually exclude sources
  • fix race condition where no module is returned from processing module
  • fix position of standalong semicolon in runtime code

Features

  • add support for @import to extenal CSS when using experimental CSS in node
  • add i64 support to the deprecated WASM implementation

Developer Experience

  • expose EnableWasmLoadingPlugin
  • add more typings
  • generate getters instead of readonly properties in typings to allow overriding them

v5.74.0

Features

  • add resolve.extensionAlias option which allows to alias extensions
    • This is useful when you are forced to add the .js extension to imports when the file really has a .ts extension (typescript + "type": "module")
  • add support for ES2022 features like static blocks
  • add Tree Shaking support for ProvidePlugin

Bugfixes

  • fix persistent cache when some build dependencies are on a different windows drive
  • make order of evaluation of side-effect-free modules deterministic between concatenated and non-concatenated modules
  • remove left-over from debugging in TLA/async modules runtime code
  • remove unneeded extra 1s timestamp offset during watching when files are actually untouched
    • This sometimes caused an additional second build which are not really needed
  • fix shareScope option for ModuleFederationPlugin
  • set "use-credentials" also for same origin scripts

Performance

  • Improve memory usage and performance of aggregating needed files/directories for watching
    • This affects rebuild performance

Extensibility

  • export HarmonyImportDependency for plugins

v5.73.0

... (truncated)

Commits

Updates gatsby-plugin-sass from 2.8.0 to 6.3.1

Release notes

Sourced from gatsby-plugin-sass's releases.

v5.3.0

Welcome to [email protected] release (December 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.2.0

Welcome to [email protected] release (November 2022 #3)

This is an out of band release due to the removal of the Potrace library in Gatsby. We'll continue with our biweekly schedule as normal.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.1.0

Welcome to [email protected] release (November 2022 #2)

This is the first minor release after the recent major release of Gatsby 5! We are focused on your feedback and implementing fixes as needed.

If you haven’t migrated yet, please refer to the migration guide. We’ve done our best to make the transition smooth!

Some brief notes about what Gatsby 5 brings to the table:

  • Slices API unlocks up to 90% reduction in build duration for content changes in highly shared components
  • Partial Hydration allows you to ship only the necessary JavaScript to the browser

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.0.0

Welcome to [email protected] release (November 2022 #1)

Key highlights of this release:

Major dependency updates:

... (truncated)

Changelog

Sourced from gatsby-plugin-sass's changelog.

6.3.1 (2022-12-14)

Note: Version bump only for package gatsby-plugin-sass

6.3.0 (2022-12-13)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-sass

6.2.0 (2022-11-25)

🧾 Release notes

Other Changes

6.1.0 (2022-11-22)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-sass

6.0.0 (2022-11-08)

🧾 Release notes

Chores

5.24.0 (2022-09-27)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-sass

5.23.1 (2022-09-22)

Note: Version bump only for package gatsby-plugin-sass

5.23.0 (2022-09-13)

🧾 Release notes

Chores

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by marvinjudehk, a new releaser for gatsby-plugin-sass since your current version.


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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

…n-mdx, webpack and gatsby-plugin-sass

Bumps [json5](https://github.com/json5/json5) to 2.2.3 and updates ancestor dependencies [json5](https://github.com/json5/json5), [gatsby](https://github.com/gatsbyjs/gatsby), [gatsby-plugin-manifest](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-manifest), [gatsby-plugin-mdx](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-mdx), [webpack](https://github.com/webpack/webpack) and [gatsby-plugin-sass](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-sass). These dependencies need to be updated together.


Updates `json5` from 2.2.0 to 2.2.3
- [Release notes](https://github.com/json5/json5/releases)
- [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md)
- [Commits](json5/json5@v2.2.0...v2.2.3)

Updates `gatsby` from 2.32.13 to 5.3.3
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/compare/[email protected]@5.3.3)

Updates `gatsby-plugin-manifest` from 2.12.1 to 5.3.1
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-manifest/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/[email protected]/packages/gatsby-plugin-manifest)

Updates `gatsby-plugin-mdx` from 1.10.1 to 5.3.1
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-mdx/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/[email protected]/packages/gatsby-plugin-mdx)

Updates `webpack` from 4.46.0 to 5.75.0
- [Release notes](https://github.com/webpack/webpack/releases)
- [Commits](webpack/webpack@v4.46.0...v5.75.0)

Updates `gatsby-plugin-sass` from 2.8.0 to 6.3.1
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-sass/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/[email protected]/packages/gatsby-plugin-sass)

---
updated-dependencies:
- dependency-name: json5
  dependency-type: indirect
- dependency-name: gatsby
  dependency-type: direct:production
- dependency-name: gatsby-plugin-manifest
  dependency-type: direct:production
- dependency-name: gatsby-plugin-mdx
  dependency-type: direct:production
- dependency-name: webpack
  dependency-type: indirect
- dependency-name: gatsby-plugin-sass
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 2, 2023
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants