Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency flow-bin to ^0.69.0 #43

Merged
merged 1 commit into from
Mar 29, 2018

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 28, 2018

This Pull Request updates dependency flow-bin from ^0.68.0 to ^0.69.0

Commits

v0.69.0


This PR has been generated by Renovate Bot.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 28, 2018

Lock file problem

Renovate failed when attempting to generate a lock file. This is usually happens when you have private modules but have not added configuration for private module support. It is strongly recommended that you do not merge this PR as-is.

Renovate will not retry generating a lockfile for this PR unless either (a) the package.json in this branch needs updating, or (b) you rename then delete this PR unmerged, so that it can be regenerated.

The output from stderr is included below:

package-lock.json
npm ERR! Unexpected token } in JSON at position 65246 while parsing near '...IfVXU2KKci/I=",
npm ERR!     },
npm ERR!     "check-error"...'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2018-03-28T23_08_00_716Z-debug.log

@coveralls
Copy link

coveralls commented Mar 28, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 3870fa2 on renovate/flow-bin-0.x into 0287df7 on master.

@renovate renovate bot merged commit e9d493b into master Mar 29, 2018
@renovate renovate bot deleted the renovate/flow-bin-0.x branch March 29, 2018 00:07
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.

None yet

2 participants