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 gatsby from 4.17.2 to 4.18.0 #143

Merged
merged 1 commit into from
Jul 11, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 11, 2022

Bumps gatsby from 4.17.2 to 4.18.0.

Release notes

Sourced from gatsby's releases.

v4.18

Welcome to gatsby@4.18.0 release (July 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

Commits
  • 2046e02 chore(release): Publish
  • bd027c8 chore(gatsby): Remove MDX resolutions (#36010)
  • d436866 test(gatsby): fix tests setup for queries after using babel-plugin-lodash (#3...
  • 96c28bf fix(gatsby-source-wordpress): always hydrate images and use the right parent ...
  • 35ac324 chore(gatsby): Move memory benchmark to generic benchmark, add support for de...
  • b2ff581 chore: Update lock file
  • f5b7c46 fix(deps): update starters and examples gatsby packages to ^4.17.2 (#36004)
  • c2d3336 fix(deps): update dependency got to ^11.8.5 for gatsby-plugin-sharp (#35800)
  • ecff91d chore(deps): update dependency msw to ^0.42.0 for gatsby-plugin-utils (#35807)
  • f645928 fix(deps): update dependency got to ^11.8.5 for gatsby-source-drupal (#35801)
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [gatsby](https://github.com/gatsbyjs/gatsby) from 4.17.2 to 4.18.0.
- [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/gatsby@4.17.2...gatsby@4.18.0)

---
updated-dependencies:
- dependency-name: gatsby
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the ⬆⬇ dependencies Pull requests that update a dependency file label Jul 11, 2022
@Robdel12 Robdel12 merged commit ed81de3 into master Jul 11, 2022
@Robdel12 Robdel12 deleted the dependabot/npm_and_yarn/gatsby-4.18.0 branch July 11, 2022 13:23
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.

1 participant