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 can-component is breaking the build 🚨 #87

Open
greenkeeper bot opened this issue Jun 23, 2017 · 1 comment
Open

An in-range update of can-component is breaking the build 🚨 #87

greenkeeper bot opened this issue Jun 23, 2017 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Jun 23, 2017

Version 3.1.0 of can-component just got published.

Branch Build failing 🚨
Dependency can-component
Current Version 3.0.7
Type dependency

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

can-component is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 7 commits.

  • 41bdf07 Update dist for release
  • 1cc5728 changing postversion script back
  • 6d995ce Do Not Merge - can-reflect (#108)
  • d4e0bd0 Merge pull request #106 from canjs/102-remove-empty-pages
  • 28aae41 Remove old tags that cause empty pages to created. Closes #102
  • 602f483 Merge pull request #99 from canjs/98-template-to-view
  • b27436f Updated references to template with view. Resolves #98

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 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Jun 23, 2017

After pinning to 3.0.7 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

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

0 participants