-
Notifications
You must be signed in to change notification settings - Fork 0
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 loader.js is breaking the build 🚨 #19
Comments
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 🚨 |
Version 4.2.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.4.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 8 commits0.
false See the full diff |
Version 4.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Version 4.5.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.6.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.7.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 9 commits.
See the full diff |
Version 4.2.0 of loader.js just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As loader.js 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 14 commits .
cc53069
release v4.2.0
1a453d3
Merge pull request #104 from trentmwillis/redefine
93478ef
Improve redefinition scenarios
e289916
Fix test:dev command
287a487
Merge pull request #105 from trentmwillis/clarify
cda1c29
Clarify prime comment
562ecf1
Merge pull request #100 from jrowlingson/master
6a9b916
remove petal references
b609262
Merge pull request #95 from chadhietala/heimdall-instrumentation
c49296d
Instrument with heimdall
453fe8c
Merge pull request #97 from Turbo87/ci-deploy
37fef79
CI: Enable automatic NPM deployment for tags
c4f0755
Merge pull request #96 from chadhietala/dict-registry
8a34296
Use dict for registery and seen to avoid filling IC cache
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: