search

danibram / mocker-data-generator

A simplified way to generate masive mock data based on a schema, you can use the awesome fake/random data generators like (FakerJs, ChanceJs, CasualJs and RandExpJs)
https://danibram.github.io/mocker-data-generator/
MIT License
426 stars 45 forks source link

An in-range update of next is breaking the build 🚨 #36

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 4.1.3 of next was just published.

Branch Build failing 🚨
Dependency next
Current Version 4.1.2
Type devDependency

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

next is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/danibram/mocker-data-generator/build/217) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/danibram/mocker-data-generator/builds/291071833?utm_source=github_status&utm_medium=notification)
Release Notes 4.1.3

Patches

  • Render error as errorHtml - Fixes an issue where styles render out of line after hot reloading: #3142
  • Strip ansi codes when logging client side - Client side webpack errors are now readable: #3138
  • [chore] Examples: styled-jsx-plugin-sass@0.2.0, show dynamic: #3137
  • "download" to "downloads" when subject is singular: #3140

Credits

Huge thanks to @timneutkens, @JeromeFitz and @trautlein for their help!

Commits

The new version differs by 5 commits.

  • 9805231 Release 4.1.3
  • 8e55adf Render error as errorHtml (#3142)
  • 4d2ea0c "download" to "downloads" when subject is singular (#3140)
  • a28bbb0 Strip ansi codes when logging client side (#3138)
  • 89691cb [chore] Examples: styled-jsx-plugin-sass@0.2.0, show dynamic (#3137)

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

After pinning to 4.1.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

danibram commented 6 years ago

The build was failing for others reasons