Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Jun 21, 2022

This PR contains the following updates:

Package Change Age Confidence
gatsby (source, changelog) 4.16.0 -> 4.25.9 age confidence

Release Notes

gatsbyjs/gatsby (gatsby)

v4.25.9

Compare Source

v4.25.8

Compare Source

v4.25.7

Compare Source

v4.25.6

Compare Source

v4.25.5

Compare Source

v4.25.4

Compare Source

v4.25.3

Compare Source

v4.25.2

Compare Source

v4.25.1

Compare Source

v4.25.0

Compare Source

v4.24.8

Compare Source

v4.24.7

Compare Source

v4.24.6

Compare Source

v4.24.5

Compare Source

v4.24.4

Compare Source

v4.24.3

Compare Source

v4.24.2

Compare Source

v4.24.1

Compare Source

v4.24.0: v4.24

Compare Source

Welcome to gatsby@4.24.0 release (September 2022 #2)

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

v4.23.1

Compare Source

v4.23.0: v4.23

Compare Source

Welcome to gatsby@4.23.0 release (September 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

v4.22.1

Compare Source

v4.22.0: v4.22

Compare Source

Welcome to gatsby@4.22.0 release (August 2022 #3)

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

v4.21.1

Compare Source

v4.21.0: v4.21

Compare Source

Welcome to gatsby@4.21.0 release (August 2022 #2)

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

v4.20.0: v4.20

Compare Source

Welcome to gatsby@4.20.0 release (August 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

v4.19.2

Compare Source

v4.19.1

Compare Source

v4.19.0: v4.19

Compare Source

Welcome to gatsby@4.19.0 release (July 2022 #2)

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

v4.18.2

Compare Source

v4.18.1

Compare Source

v4.18.0: v4.18

Compare Source

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

v4.17.2

Compare Source

v4.17.1

Compare Source

v4.17.0: v4.17

Compare Source

Welcome to gatsby@4.17.0 release (June 2022 #2)

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency gatsby to v4.17.0 Update dependency gatsby to v4.17.1 Jun 24, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch 2 times, most recently from 4baef27 to 066c24b Compare June 29, 2022 03:52
@renovate renovate bot changed the title Update dependency gatsby to v4.17.1 Update dependency gatsby to v4.17.2 Jun 29, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from 066c24b to deb488f Compare July 5, 2022 19:29
@renovate renovate bot changed the title Update dependency gatsby to v4.17.2 Update dependency gatsby to v4.18.0 Jul 5, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from deb488f to 90f2fa7 Compare July 12, 2022 17:06
@renovate renovate bot changed the title Update dependency gatsby to v4.18.0 Update dependency gatsby to v4.18.1 Jul 12, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from 90f2fa7 to e259901 Compare July 13, 2022 17:05
@renovate renovate bot changed the title Update dependency gatsby to v4.18.1 Update dependency gatsby to v4.18.2 Jul 13, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from e259901 to c671af4 Compare July 19, 2022 09:41
@renovate renovate bot changed the title Update dependency gatsby to v4.18.2 Update dependency gatsby to v4.19.0 Jul 19, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from c671af4 to ef8b2bc Compare July 20, 2022 13:40
@renovate renovate bot changed the title Update dependency gatsby to v4.19.0 Update dependency gatsby to v4.19.1 Jul 20, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from ef8b2bc to 759e3b9 Compare July 21, 2022 13:57
@renovate renovate bot changed the title Update dependency gatsby to v4.19.1 Update dependency gatsby to v4.19.2 Jul 21, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from 759e3b9 to 05f1080 Compare August 2, 2022 21:18
@renovate renovate bot changed the title Update dependency gatsby to v4.19.2 Update dependency gatsby to v4.20.0 Aug 2, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from 05f1080 to a8f8537 Compare August 16, 2022 15:06
@renovate renovate bot changed the title Update dependency gatsby to v4.20.0 Update dependency gatsby to v4.21.0 Aug 16, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from a8f8537 to 1cd607a Compare November 20, 2022 15:28
@renovate renovate bot changed the title Update dependency gatsby to v4.21.0 Update dependency gatsby to v4.24.8 Nov 20, 2022
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from 1cd607a to 33d20c9 Compare March 16, 2023 21:43
@renovate renovate bot changed the title Update dependency gatsby to v4.24.8 Update dependency gatsby to v4.25.5 Mar 16, 2023
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from 0b80c0a to 8155e71 Compare May 28, 2023 15:54
@renovate renovate bot changed the title Update dependency gatsby to v4.25.5 Update dependency gatsby to v4.25.7 May 28, 2023
@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from 8155e71 to be311eb Compare December 20, 2023 05:23
@renovate renovate bot changed the title Update dependency gatsby to v4.25.7 Update dependency gatsby to v4.25.8 Dec 20, 2023
@renovate
Copy link
Author

renovate bot commented Dec 20, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from be311eb to b7c09a4 Compare May 23, 2024 18:02
@renovate renovate bot changed the title Update dependency gatsby to v4.25.8 Update dependency gatsby to v4.25.9 May 23, 2024
@renovate
Copy link
Author

renovate bot commented May 23, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant