-
Notifications
You must be signed in to change notification settings - Fork 0
An in-range update of postprocessing is breaking the build 🚨 #36
Comments
After pinning to 6.3.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 13 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v6.4.0Requires ChangelogPasses
Materials
Effects
CommitsThe new version differs by 7 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v6.5.0Requires ChangelogEffects
See #132 for details. Materials
CommitsThe new version differs by 25 commits.
There are 25 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v6.5.1Requires CommitsThe new version differs by 33 commits.
There are 33 commits in total. See the full diff |
The dependency postprocessing was updated from
6.3.1
to6.3.2
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
postprocessing 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
Release Notes for v6.3.2
Requires
three
≥ 0.102.0 < 0.105.0Changelog
Effects
updateWorldMatrix
instead ofupdateMatrixWorld
.Miscellaneous
Commits
The new version differs by 4 commits.
10a9f74
Update rollup.config.js
60cf36c
Replace rollup-plugin-string with rollup-plugin-glsl.
fa1b238
Use updateWorldMatrix.
4f43536
Version 6.3.1.
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 🌴
The text was updated successfully, but these errors were encountered: