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

An in-range update of resolve is breaking the build 🚨 #255

Closed
greenkeeper bot opened this issue Dec 19, 2019 · 5 comments
Closed

An in-range update of resolve is breaking the build 🚨 #255

greenkeeper bot opened this issue Dec 19, 2019 · 5 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 19, 2019

The dependency resolve was updated from 1.14.0 to 1.14.1.

🚨 View failing branch.

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

resolve is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

  • 7eb98ea 1.14.1
  • fe73a76 [Fix] core: wasi was mistakenly available as a core module in v13.4.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 19, 2019

After pinning to 1.14.0 your tests are passing again. Downgrade this dependency 📌.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 5, 2020

  • The dependency resolve was updated from 1.15.0 to 1.15.1.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

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

  • c1750d6 v1.15.1
  • 5e1f5c8 [Dev Deps] update @ljharb/eslint-config
  • 891bd89 [Fix] correct behavior when requiring . with same name (#212)
  • 16c1170 [Tests] allow node 5 on windows to fail due to npm registry bug
  • 9529db4 v1.15.0
  • f0ad85f [Dev Deps] update eslint, @ljharb/eslint-config, tape
  • 7b80058 [Refactor] sync: add function name
  • 163f9da [New] sync'/async: Implement packageIterator (#205)
  • fca4013 [Refactor] remove useless exports assignment
  • 9fea81a v1.14.2
  • b261110 [Fix] sync/async: Fixes isCore check (#206)
  • 2f0e047 v1.14.1

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 15, 2020

  • The dependency resolve was updated from 1.15.1 to 1.16.0.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

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

  • 301c07d v1.16.0
  • 1fc4bf4 [New] core: fs/promises is a core module again in node 14+ (f6473e2)
  • bab1166 [patch] sync/async: use native realpath if available to unwrap symlinks (#217)
  • c1750d6 v1.15.1
  • 5e1f5c8 [Dev Deps] update @ljharb/eslint-config
  • 891bd89 [Fix] correct behavior when requiring . with same name (#212)
  • 16c1170 [Tests] allow node 5 on windows to fail due to npm registry bug
  • 9529db4 v1.15.0
  • f0ad85f [Dev Deps] update eslint, @ljharb/eslint-config, tape
  • 7b80058 [Refactor] sync: add function name
  • 163f9da [New] sync'/async: Implement packageIterator (#205)
  • fca4013 [Refactor] remove useless exports assignment
  • 9fea81a v1.14.2
  • b261110 [Fix] sync/async: Fixes isCore check (#206)
  • 2f0e047 v1.14.1

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 17, 2020

  • The dependency resolve was updated from 1.16.0 to 1.16.1.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

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

  • ac3eb2f v1.16.1
  • 782dfec [patch] when a non-node fs is broken and lacks realpath/realpathSync, do not crash (#220)
  • 301c07d v1.16.0
  • 1fc4bf4 [New] core: fs/promises is a core module again in node 14+ (f6473e2)
  • bab1166 [patch] sync/async: use native realpath if available to unwrap symlinks (#217)
  • c1750d6 v1.15.1
  • 5e1f5c8 [Dev Deps] update @ljharb/eslint-config
  • 891bd89 [Fix] correct behavior when requiring . with same name (#212)
  • 16c1170 [Tests] allow node 5 on windows to fail due to npm registry bug
  • 9529db4 v1.15.0
  • f0ad85f [Dev Deps] update eslint, @ljharb/eslint-config, tape
  • 7b80058 [Refactor] sync: add function name
  • 163f9da [New] sync'/async: Implement packageIterator (#205)
  • fca4013 [Refactor] remove useless exports assignment
  • 9fea81a v1.14.2

There are 17 commits in total.

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 22, 2020

  • The dependency resolve was updated from 1.16.1 to 1.17.0.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

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

  • 3a76ef8 v1.17.0
  • 4d9e8e8 [Dev Deps] update tape
  • 52348f1 [New] sync/async: add realpath/realpathSync options (#218)
  • ac3eb2f v1.16.1
  • 782dfec [patch] when a non-node fs is broken and lacks realpath/realpathSync, do not crash (#220)
  • 301c07d v1.16.0
  • 1fc4bf4 [New] core: fs/promises is a core module again in node 14+ (f6473e2)
  • bab1166 [patch] sync/async: use native realpath if available to unwrap symlinks (#217)
  • c1750d6 v1.15.1
  • 5e1f5c8 [Dev Deps] update @ljharb/eslint-config
  • 891bd89 [Fix] correct behavior when requiring . with same name (#212)
  • 16c1170 [Tests] allow node 5 on windows to fail due to npm registry bug
  • 9529db4 v1.15.0
  • f0ad85f [Dev Deps] update eslint, @ljharb/eslint-config, tape
  • 7b80058 [Refactor] sync: add function name

There are 20 commits in total.

See the full diff

@xg-wang xg-wang closed this as completed Feb 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant