You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was foolish enough to commit directly to master and i accidentally typed part of the commit message into package.json. Needless to say, this meant the JSON was invalid. The result: Dependabot closed the one pull request that was still open, stating it detected that the dependency is now up to date and the PR is no longer needed.
So this seems to be a small bug which occurs when it tries to parse invalid JSON. Or, of course, it's completely unrelated and the timing is just coincidental... you never really know.
If you type my github username in your email client you'll find previous conversations which will direct you to our github organisation, the repository in question ends with -Tests and the pull request number is 47. Hopefully you'll be able to pull some data and fix this if it really is caused by invalid JSON.
The text was updated successfully, but these errors were encountered:
StephanBijzitter
changed the title
Invalid JSON in package.json results in Dependabot goofing out
Invalid JSON in package.json results in Dependabot closing pull requests
Dec 18, 2017
I was foolish enough to commit directly to master and i accidentally typed part of the commit message into
package.json
. Needless to say, this meant the JSON was invalid. The result: Dependabot closed the one pull request that was still open, stating it detected that the dependency is now up to date and the PR is no longer needed.So this seems to be a small bug which occurs when it tries to parse invalid JSON. Or, of course, it's completely unrelated and the timing is just coincidental... you never really know.
If you type my github username in your email client you'll find previous conversations which will direct you to our github organisation, the repository in question ends with
-Tests
and the pull request number is 47. Hopefully you'll be able to pull some data and fix this if it really is caused by invalid JSON.The text was updated successfully, but these errors were encountered: