takuyahara / greenkeeper-monorepo-issue Goto Github PK

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.38 to 2.0.39.

• The dependency gatsby-plugin-manifest was updated from 2.0.28 to 2.0.29.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.11 to 3.0.12.
• The dependency gatsby-plugin-sharp was updated from 2.0.34 to 2.0.35.
• The dependency gatsby-source-filesystem was updated from 2.0.29 to 2.0.30.
• The dependency gatsby-transformer-sharp was updated from 2.1.17 to 2.1.18.
• The dependency gatsby was updated from 2.3.25 to 2.3.26.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ Travis CI - Branch: The build errored.

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.39 to 2.0.40.

• The dependency gatsby-plugin-manifest was updated from 2.0.28 to 2.0.29.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.11 to 3.0.12.
• The dependency gatsby-plugin-sharp was updated from 2.0.34 to 2.0.35.
• The dependency gatsby-source-filesystem was updated from 2.0.30 to 2.0.31.
• The dependency gatsby-transformer-sharp was updated from 2.1.17 to 2.1.18.
• The dependency gatsby was updated from 2.3.26 to 2.3.27.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ Travis CI - Branch: The build errored.

---

Commits

The new version differs by 399 commits.

• 0efca77 chore(release): Publish
• 7447d10 Fix linting for new version of Prettier
• 7d4c28d chore: update minor updates in packages (#19248)
• ac5af97 docs: adding rehydration doc and updates to building apps over… (#19214)
• 1acac83 update a few reference guide overview pages (#19296)
• 77d25da fix(gatsby-theme-blog): fix avatar squishing on mobile (#19172) (#19236)
• f228998 docs(gatsby-transformer-remark): Fix typo (#19237)
• 16e61d1 fix(blog-starter): remove unused query field from blog-post te… (#19328)
• 3244477 chore(showcase): Add Mieke Frouws portfolio (#19259)
• d4b02a0 chore(showcase): Added binaria.com (#19364)
• 496c51b blog(offline support): links add new and better text (#19360)
• 3e2c8f9 chore(showcase): Add The Fabulous Lifestyles website (#19327)
• ae3042c chore(showcase): Add peluqueriavenezolana.cl (#19221)
• 4e2fe45 fix(scripts/i18n): fix grabbing commit sha and message (#19340)
• 6f422b0 chore(showcase): remove not whitelisted categories from entries (#19341)

There are 250 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.38 to 2.0.39.

• The dependency gatsby-plugin-manifest was updated from 2.0.28 to 2.0.29.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.11 to 3.0.12.
• The dependency gatsby-plugin-sharp was updated from 2.0.34 to 2.0.35.
• The dependency gatsby-source-filesystem was updated from 2.0.29 to 2.0.30.
• The dependency gatsby-transformer-sharp was updated from 2.1.17 to 2.1.18.
• The dependency gatsby was updated from 2.3.25 to 2.3.26.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ Travis CI - Branch: The build errored.

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.38 to 2.0.39.

• The dependency gatsby-plugin-manifest was updated from 2.0.28 to 2.0.29.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.11 to 3.0.12.
• The dependency gatsby-plugin-sharp was updated from 2.0.34 to 2.0.35.
• The dependency gatsby-source-filesystem was updated from 2.0.29 to 2.0.30.
• The dependency gatsby-transformer-sharp was updated from 2.1.17 to 2.1.18.
• The dependency gatsby was updated from 2.3.25 to 2.3.26.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ Travis CI - Branch: The build errored.

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

There have been updates to the react monorepo:

• • The dependency react was updated from 16.12.0 to 16.13.0.

• The dependency react-dom was updated from 16.12.0 to 16.13.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ Travis CI - Branch: The build errored.

---

Release Notes for 16.13.0 (February 26, 2020)

React

• Warn when a string ref is used in a manner that's not amenable to a future codemod (@lunaruan in #17864)
• Deprecate React.createFactory() (@trueadm in #17878)

React DOM

• Warn when changes in style may cause an unexpected collision (@sophiebits in #14181, #18002)
• Warn when a function component is updated during another component's render phase (@acdlite in #17099)
• Deprecate unstable_createPortal (@trueadm in #17880)
• Fix onMouseEnter being fired on disabled buttons (@AlfredoGJ in #17675)
• Call shouldComponentUpdate twice when developing in StrictMode (@bvaughn in #17942)
• Add version property to ReactDOM (@ealush in #15780)
• Don't call toString() of dangerouslySetInnerHTML (@sebmarkbage in #17773)
• Show component stacks in more warnings (@gaearon in #17922, #17586)

Concurrent Mode (Experimental)

• Warn for problematic usages of ReactDOM.createRoot() (@trueadm in #17937)
• Remove ReactDOM.createRoot() callback params and added warnings on usage (@bvaughn in #17916)
• Don't group Idle/Offscreen work with other work (@sebmarkbage in #17456)
• Adjust SuspenseList CPU bound heuristic (@sebmarkbage in #17455)
• Add missing event plugin priorities (@trueadm in #17914)
• Fix isPending only being true when transitioning from inside an input event (@acdlite in #17382)
• Fix React.memo components dropping updates when interrupted by a higher priority update (@acdlite in #18091)
• Don't warn when suspending at the wrong priority (@gaearon in #17971)
• Fix a bug with rebasing updates (@acdlite and @sebmarkbage in #17560, #17510, #17483, #17480)

Artifacts

• react: https://unpkg.com/[email protected]/umd/
• react-art: https://unpkg.com/[email protected]/umd/
• react-dom: https://unpkg.com/[email protected]/umd/
• react-is: https://unpkg.com/[email protected]/umd/
• react-test-renderer: https://unpkg.com/[email protected]/umd/
• scheduler: https://unpkg.com/[email protected]/umd/

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.