An in-range update of graceful-fs is breaking the build 🚨 about detect-flowtype-js

[greenkeeper]

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

[greenkeeper]

• The dependency graceful-fs was updated from 4.2.0 to 4.2.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 4 commits ahead by 4, behind by 1.

• 7e8a560 4.2.1
• e660ced Fix util.promisify for patched read function
• 05bc069 update deps
• 72eb282 4.2.0

See the full diff

[greenkeeper]

• The dependency graceful-fs was updated from 4.2.1 to 4.2.2.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 9 commits ahead by 9, behind by 4.

• 5552309 4.2.2
• 9841d47 Do not inadvertently monkeypatch fs streams
• bbb8e17 Hide fs.close and fs.closeSync previous symbols
• 770ee51 Add Node.js 0.x polyfill for global retry queue name
• 20b77c4 Create/use global shared retry queue.
• 841bf6d 4.2.1
• 1139b6f Fix util.promisify for patched read function
• a4520b4 update deps
• 585df78 4.2.0

See the full diff

[greenkeeper]

• The dependency graceful-fs was updated from 4.2.2 to 4.2.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• 79aa9dd 4.2.3
• 65c6638 Split legacy stream properties from regular ones.

See the full diff

[greenkeeper]

• The dependency graceful-fs was updated from 4.2.3 to 4.2.4.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• 5a29f6c 4.2.4
• 9f66560 fix: attach queue to fs module in addition to global

See the full diff