New version of assetgraph (4.9.1) broke the build

[depfu[bot]]

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/ range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
assetgraph	^4.0.0	4.9.1

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure potentially will also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of assetgraph for this test run.

What changed?

✳️ assetgraph ( → 4.9.1) · Repo

Commits

See the full diff on Github. The new version differs by 2 commits:

• 4.9.1
• Dumb down another query in moveAssetsInOrder

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

[coveralls]

Coverage remained the same at 83.041% when pulling 4d38170ec5977acc81a0e3e7971d3496c1a55314 on depfu/check/npm/assetgraph-4.9.1 into 3780e496e5c4f77b91e2e92fa6d37d95825e1535 on master.

[papandreou]

Temporary glitch, it seems. I'm happy with keeping it at ^4.0.0, so closing this.