chore(deps): update gatsby monorepo (major) #177

The whole team took time off for a much deserved winter break and we hope you had relaxing holidays, too! Before the break we spent time doing maintenance work such as updating internal dependencies or fixing some smaller bugs here and there. In case you missed it, we shipped ES Modules (ESM) in Gatsby files in the last release.

So check out the notable bugfixes section to learn more.

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.3.3`

Compare Source

`v5.3.2`

Compare Source

`v5.3.1`

Compare Source

`v5.3.0`: v5.3.0

Compare Source

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`: v5.2.0

Compare Source

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`: v5.1.0

Compare Source

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.1`

Compare Source

`v5.0.0`: v5.0.0

Compare Source

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

Key highlights of this release:

Slice API - Only re-build individual slices of your page
Partial Hydration (Beta) - Improve frontend performance by shipping less JavaScript
GraphiQL v2 - An all new UI with features like dark mode, tabs, and persisted state
Performance Improvements

Major dependency updates:

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

`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 [email protected] 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 [email protected] release (September 2022 #1)

Key highlights of this release:

Open RFCs

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 [email protected] release (August 2022 #3)

Key highlights of this release:

Open RFCs

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 [email protected] 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 [email protected] release (August 2022 #1)

Key highlights of this release:

RFC for changes in sort and aggregation fields in Gatsby GraphQL Schema
Release Candidate for gatsby-plugin-mdx v4 - Support for MDX v2 and more!

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 [email protected] release (July 2022 #2)

Key highlights of this release:

Gatsby Head API - Better performance & more future-proof than react-helmet
Release Candidate for gatsby-plugin-mdx v4 - Support for MDX v2 and more!

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 [email protected] release (July 2022 #1)

Key highlights of this release:

typesOutputPath option for GraphQL Typegen - Configure the location of the generated TypeScript types
Server Side Rendering (SSR) in development - Find bugs & hydration errors more easily during gatsby develop
Open RFCs - MDX v2 & Metadata management

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 [email protected] 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

`v4.16.0`: v4.16

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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.15.2`

Compare Source

`v4.15.1`

Compare Source

`v4.15.0`: v4.15

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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][full-changelog]

`v4.14.1`

Compare Source

`v4.14.0`: v4.14

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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.13.1`

Compare Source

`v4.13.0`: v4.13

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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.12.1`

Compare Source

`v4.12.0`: v4.12

Compare Source

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

Key highlights of this release:

New RFCs

Also check out notable bugfixes.

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.11.3`

Compare Source

`v4.11.2`

Compare Source

`v4.11.1`

Compare Source

`v4.11.0`: v4.11

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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.10.3`

Compare Source

`v4.10.2`

Compare Source

`v4.10.1`

Compare Source

`v4.10.0`: v4.10

Compare Source

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

Key highlights of this release:

Image CDN

Also check out notable bugfixes.

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.9.3`

Compare Source

`v4.9.2`

Compare Source

`v4.9.1`

Compare Source

`v4.9.0`: v4.9

Compare Source

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

Key highlights of this release:

Support for TypeScript in gatsby-config and gatsby-node

Also check out notable bugfixes.

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.8.2`

Compare Source

`v4.8.1`

Compare Source

`v4.8.0`: v4.8

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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.7.2`

Compare Source

`v4.7.1`

Compare Source

`v4.7.0`: v4.7

Compare Source

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

Key highlights of this release:

trailingSlash Option - Now built into the Framework itself
Faster Schema Creation & createPages - Speed improvements of at least 30%

Also check out notable bugfixes.

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.6.2`

Compare Source

`v4.6.1`

Compare Source

`v4.6.0`: v4.6

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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.5.5`

Compare Source

`v4.5.4`

Compare Source

`v4.5.3`

Compare Source

`v4.5.2`

Compare Source

`v4.5.1`

Compare Source

`v4.5.0`: v4.5

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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.4.0`: v4.4

Compare Source

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

Key highlights of this release:

Detect Node Mutations

Also check out notable bugfixes.

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.3.0`: v4.3

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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.2.0`: v4.2

Compare Source

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

Key highlights of this release:

Also check out notable bugfixes.

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.1.6`

Compare Source

`v4.1.5`

Compare Source

`v4.1.4`

Compare Source

`v4.1.3`

Compare Source

`v4.1.2`

Compare Source

`v4.1.1`

Compare Source

`v4.1.0`: v4.1

[Compare Source](https://redirect.github.com/gatsbyjs/gatsby/compare/5505c478ccbd59863cdcf2e55404b54ee000d73e...4086ca523

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

renovate · 2021-04-26T12:39:13Z

⚠️ 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 check 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

npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN old lockfile Error: Integrity checksum failed when using sha512: wanted sha512-ZUj2lkUDLjwJaGu4WD0dYSvsfIyhQt2l/AJDlg4ij+rCDU3fSFKgHWanNovViUoaWHAxgrpft3KGFfvWPZH5LA== but got sha512-StCz3QY8lxTb5cl2HJxjwLFOXPIFQp+p+hxQfc8WE0QiLfCtIlKj8/+5tjjKm8uSTlAW+fCPaavGFS06V9Ar3A==.
npm WARN old lockfile     at /home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/pacote/lib/registry.js:145:39
npm WARN old lockfile     at async Array.<anonymous> (/home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:709:9)
npm WARN old lockfile  Could not fetch metadata for [email protected] Error: Integrity checksum failed when using sha512: wanted sha512-ZUj2lkUDLjwJaGu4WD0dYSvsfIyhQt2l/AJDlg4ij+rCDU3fSFKgHWanNovViUoaWHAxgrpft3KGFfvWPZH5LA== but got sha512-StCz3QY8lxTb5cl2HJxjwLFOXPIFQp+p+hxQfc8WE0QiLfCtIlKj8/+5tjjKm8uSTlAW+fCPaavGFS06V9Ar3A==.
npm WARN old lockfile     at /home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/pacote/lib/registry.js:145:39
npm WARN old lockfile     at async Array.<anonymous> (/home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:709:9) {
npm WARN old lockfile   code: 'EINTEGRITY'
npm WARN old lockfile }
npm WARN old lockfile Error: Integrity checksum failed when using sha512: wanted sha512-GfG8Vh/jMcnJKDpv7T6O1pS/WVqiocjPQ9o9cscW8bjR9W36DT3Xb4pDZT70t1xyVvX48/NrTQGz0H7I3fCLhQ== but got sha512-D0Ufv1ExCAmF38P2Uh1lwpminZFRXEINJe53zRAbm4KPwSyd6DY/uDoS0Blj9jvPpn1+wivKpZYc8aAAN/nAkg==.
npm WARN old lockfile     at /home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/pacote/lib/registry.js:145:39
npm WARN old lockfile     at async Array.<anonymous> (/home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:709:9)
npm WARN old lockfile  Could not fetch metadata for [email protected] Error: Integrity checksum failed when using sha512: wanted sha512-GfG8Vh/jMcnJKDpv7T6O1pS/WVqiocjPQ9o9cscW8bjR9W36DT3Xb4pDZT70t1xyVvX48/NrTQGz0H7I3fCLhQ== but got sha512-D0Ufv1ExCAmF38P2Uh1lwpminZFRXEINJe53zRAbm4KPwSyd6DY/uDoS0Blj9jvPpn1+wivKpZYc8aAAN/nAkg==.
npm WARN old lockfile     at /home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/pacote/lib/registry.js:145:39
npm WARN old lockfile     at async Array.<anonymous> (/home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:709:9) {
npm WARN old lockfile   code: 'EINTEGRITY'
npm WARN old lockfile }
npm WARN old lockfile Error: Integrity checksum failed when using sha512: wanted sha512-U+PqKfBcR39RFbJrlJPFwDXG2iLOZBGOPzNSWTAGUoOfTiL8qHTkemJeyV5CcL0UyaRgR8g3S469cNWFs/SHIw== but got sha512-t7MBR28Akcp4Jm+QoR63XgAi9YgCUmgvDHqf5otgAj4QvdoBE4ImCX0ffehefePPG+aitiYHp0g/mW6s4Tp+dw==.
npm WARN old lockfile     at /home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/pacote/lib/registry.js:145:39
npm WARN old lockfile     at async Array.<anonymous> (/home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:709:9)
npm WARN old lockfile  Could not fetch metadata for [email protected] Error: Integrity checksum failed when using sha512: wanted sha512-U+PqKfBcR39RFbJrlJPFwDXG2iLOZBGOPzNSWTAGUoOfTiL8qHTkemJeyV5CcL0UyaRgR8g3S469cNWFs/SHIw== but got sha512-t7MBR28Akcp4Jm+QoR63XgAi9YgCUmgvDHqf5otgAj4QvdoBE4ImCX0ffehefePPG+aitiYHp0g/mW6s4Tp+dw==.
npm WARN old lockfile     at /home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/pacote/lib/registry.js:145:39
npm WARN old lockfile     at async Array.<anonymous> (/home/ubuntu/.npm-global/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:709:9) {
npm WARN old lockfile   code: 'EINTEGRITY'
npm WARN old lockfile }
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @dailybruin/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"16.8.6" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.9.0 || ^17.0.0" from [email protected]
npm ERR! node_modules/gatsby
npm ERR!   dev gatsby@"3.3.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-04-26T12_38_42_387Z-debug.log

renovate bot requested review from a team as code owners April 29, 2019 01:42

renovate bot changed the title ~~Update dependency gatsby-plugin-emotion to v4~~ fix(deps): update dependency gatsby-plugin-emotion to v4 May 8, 2019

renovate bot changed the title ~~fix(deps): update dependency gatsby-plugin-emotion to v4~~ Update dependency gatsby-plugin-emotion to v4 May 17, 2019

renovate bot changed the title ~~Update dependency gatsby-plugin-emotion to v4~~ fix(deps): update dependency gatsby-plugin-emotion to v4 May 17, 2019

renovate bot changed the title ~~fix(deps): update dependency gatsby-plugin-emotion to v4~~ Update dependency gatsby-plugin-emotion to v4 May 29, 2019

renovate bot changed the title ~~Update dependency gatsby-plugin-emotion to v4~~ fix(deps): update dependency gatsby-plugin-emotion to v4 May 31, 2019

renovate bot force-pushed the renovate/major-gatsby-monorepo branch 2 times, most recently from a9dc120 to 180b96a Compare May 31, 2019 22:24

renovate bot changed the title ~~fix(deps): update dependency gatsby-plugin-emotion to v4~~ Update dependency gatsby-plugin-emotion to v4 Jun 27, 2019

renovate bot changed the title ~~Update dependency gatsby-plugin-emotion to v4~~ fix(deps): update dependency gatsby-plugin-emotion to v4 Jul 27, 2019

renovate bot changed the title ~~fix(deps): update dependency gatsby-plugin-emotion to v4~~ Update dependency gatsby-plugin-emotion to v4 Aug 14, 2019

renovate bot changed the title ~~Update dependency gatsby-plugin-emotion to v4~~ fix(deps): update dependency gatsby-plugin-emotion to v4 Oct 25, 2020

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from 180b96a to 851780f Compare December 8, 2020 09:05

renovate bot changed the title ~~fix(deps): update dependency gatsby-plugin-emotion to v4~~ fix(deps): update dependency gatsby-plugin-emotion to v5 Dec 8, 2020

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from 851780f to f7f4e7e Compare April 26, 2021 12:39

renovate bot changed the title ~~fix(deps): update dependency gatsby-plugin-emotion to v5~~ chore(deps): update gatsby monorepo (major) Apr 26, 2021

renovate bot force-pushed the renovate/major-gatsby-monorepo branch 2 times, most recently from fabc085 to 6363cff Compare May 15, 2021 20:07

renovate bot force-pushed the renovate/major-gatsby-monorepo branch 2 times, most recently from 6328398 to 035abb1 Compare June 12, 2021 20:13

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from 035abb1 to 0b95723 Compare October 20, 2021 06:14

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from 0b95723 to fe5ebc4 Compare March 7, 2022 13:20

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from fe5ebc4 to c53e899 Compare March 26, 2022 14:56

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from c53e899 to ec87a75 Compare April 24, 2022 23:18

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from ec87a75 to 441a8b5 Compare May 15, 2022 18:58

renovate bot force-pushed the renovate/major-gatsby-monorepo branch 2 times, most recently from a6cd153 to 1c6b0a1 Compare June 24, 2022 00:48

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from 1c6b0a1 to bde9f46 Compare September 25, 2022 18:20

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from bde9f46 to 23f2a41 Compare November 20, 2022 14:52

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from 23f2a41 to 7be4174 Compare March 16, 2023 10:12

renovate bot force-pushed the renovate/major-gatsby-monorepo branch 2 times, most recently from be9e8f3 to 6d081a6 Compare March 29, 2023 23:02

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from 6d081a6 to 148c923 Compare May 28, 2023 10:34

renovate bot changed the title ~~chore(deps): update gatsby monorepo (major)~~ fix(deps): update dependency gatsby-plugin-emotion to v8 Jun 9, 2023

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from 148c923 to 9965398 Compare February 1, 2024 01:23

renovate bot changed the title ~~fix(deps): update dependency gatsby-plugin-emotion to v8~~ chore(deps): update gatsby monorepo (major) Feb 1, 2024

renovate bot changed the title ~~chore(deps): update gatsby monorepo (major)~~ fix(deps): update dependency gatsby-plugin-emotion to v8 Feb 1, 2024

BrysonXiao force-pushed the master branch 3 times, most recently from b36edb1 to aac0a6f Compare March 7, 2024 00:31

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from 9965398 to c543e7c Compare March 7, 2024 00:34

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from c543e7c to d9cdae5 Compare August 6, 2024 08:58

renovate bot changed the title ~~fix(deps): update dependency gatsby-plugin-emotion to v8~~ chore(deps): update gatsby monorepo (major) Aug 6, 2024

chore(deps): update gatsby monorepo

b322cbc

renovate bot force-pushed the renovate/major-gatsby-monorepo branch from d9cdae5 to b322cbc Compare November 6, 2024 22:25

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update gatsby monorepo (major) #177

chore(deps): update gatsby monorepo (major) #177

renovate bot commented Apr 29, 2019 •

edited

Loading

renovate bot commented Apr 26, 2021

chore(deps): update gatsby monorepo (major) #177

Are you sure you want to change the base?

chore(deps): update gatsby monorepo (major) #177

Conversation

renovate bot commented Apr 29, 2019 • edited Loading

Release Notes

v5.13.0: v5.13.0

v5.12.0: v5.12.0

v5.11.0: v5.11.0

v5.7.0: v5.7.0

v5.6.0: v5.6.0

v5.4.0: v5.4.0

v5.3.0: v5.3.0

v5.2.0: v5.2.0

v5.1.0: v5.1.0

v5.0.0: v5.0.0

v4.24.0: v4.24

v4.23.0: v4.23

v4.22.0: v4.22

v4.21.0: v4.21

v4.20.0: v4.20

v4.19.0: v4.19

v4.18.0: v4.18

v4.17.0: v4.17

v4.16.0: v4.16

v4.15.0: v4.15

v4.14.0: v4.14

v4.13.0: v4.13

v4.12.0: v4.12

v4.11.0: v4.11

v4.10.0: v4.10

v4.9.0: v4.9

v4.8.0: v4.8

v4.7.0: v4.7

v4.6.0: v4.6

v4.5.0: v4.5

v4.4.0: v4.4

v4.3.0: v4.3

v4.2.0: v4.2

v4.1.0: v4.1

Configuration

renovate bot commented Apr 26, 2021

⚠️ Artifact update problem

File name: package-lock.json

renovate bot commented Apr 29, 2019 •

edited

Loading

`v5.13.0`: v5.13.0

`v5.12.0`: v5.12.0

`v5.11.0`: v5.11.0

`v5.7.0`: v5.7.0

`v5.6.0`: v5.6.0

`v5.4.0`: v5.4.0

`v5.3.0`: v5.3.0

`v5.2.0`: v5.2.0

`v5.1.0`: v5.1.0

`v5.0.0`: v5.0.0

`v4.24.0`: v4.24

`v4.23.0`: v4.23

`v4.22.0`: v4.22

`v4.21.0`: v4.21

`v4.20.0`: v4.20

`v4.19.0`: v4.19

`v4.18.0`: v4.18

`v4.17.0`: v4.17

`v4.16.0`: v4.16

`v4.15.0`: v4.15

`v4.14.0`: v4.14

`v4.13.0`: v4.13

`v4.12.0`: v4.12

`v4.11.0`: v4.11

`v4.10.0`: v4.10

`v4.9.0`: v4.9

`v4.8.0`: v4.8

`v4.7.0`: v4.7

`v4.6.0`: v4.6

`v4.5.0`: v4.5

`v4.4.0`: v4.4

`v4.3.0`: v4.3

`v4.2.0`: v4.2

`v4.1.0`: v4.1