An in-range update of babel-core is breaking the build 🚨 #56
Labels
Comments
|
Should be fixed by #58 |
Eandalf7h
added a commit
to Eandalf7h/graphql
that referenced
this issue
Nov 27, 2021
Greenkeeper was complaining about these updates here: - graphql/swapi-graphql#56 - graphql/swapi-graphql#57 I fixed the underlying issue here: - graphql/swapi-graphql#58 So we should be good to go with these updates now.
hiukky7e
added a commit
to hiukky7e/graphqlb
that referenced
this issue
Nov 27, 2021
Greenkeeper was complaining about these updates here: - graphql/swapi-graphql#56 - graphql/swapi-graphql#57 I fixed the underlying issue here: - graphql/swapi-graphql#58 So we should be good to go with these updates now.
jonathan-briere
added a commit
to jonathan-briere/swapi-graphql
that referenced
this issue
Jul 4, 2023
Greenkeeper was complaining about these updates here: - graphql/swapi-graphql#56 - graphql/swapi-graphql#57 I fixed the underlying issue here: - graphql/swapi-graphql#58 So we should be good to go with these updates now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version 6.23.1 of babel-core just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As babel-core is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: