-
Notifications
You must be signed in to change notification settings - Fork 1
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 copy-webpack-plugin is breaking the build 🚨 #165
Comments
After pinning to 4.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.1.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.2.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 10 commits.
See the full diff |
Version 4.2.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.2.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 8 commits ahead by 8, behind by 2.
See the full diff |
Version 4.2.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 11 commits.
See the full diff |
Version 4.3.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 6 commits.
See the full diff |
Version 4.4.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 11 commits.
See the full diff |
Version 4.4.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.4.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.4.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.5.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.5.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 7 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Version 4.1.0 of copy-webpack-plugin just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As copy-webpack-plugin is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 36 commits ahead by 36, behind by 33.
3a95eab
chore(release): 4.1.0
73aab35
chore: Adds contrib release tooling
de46fde
fix: Memory leak in watch mode and use Set for performance (#130)
79f30ab
docs: Fix travis url
dda7ac5
docs: Update to config readme format
edabbf6
chore: Update package meta
75c6f08
chore: Adds changelog
ec44b72
chore: Change license to JS Foundation (#138)
7844603
chore(release): 4.0.1 (#96)
54545db
ci: Added Appveyor for Windows testing (#94)
405d1ec
feat: Added non-wildcard glob support
1b2c21a
fix: Fixed glob as object
ad62899
fix: Improved Windows compatibility (#85)
1a441d1
chore(release): 4.0.0 (#83)
f5d487d
refactor: Changed default concurrency to 100 for EMFILE/ENFILE issues (#82)
There are 36 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: