Skip to content

An in-range update of can-define is breaking the build 🚨 #88

@greenkeeper

Description

@greenkeeper

Version 1.2.0 of can-define just got published.

Branch Build failing 🚨
Dependency can-define
Current Version 1.0.26
Type dependency

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

can-define 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 13 commits.

  • 26d4b30 Update dist for release
  • 3fdaa23 fixing postversion script
  • 1707547 getting tests to pass with reflect apis (#165)
  • 826461d Merge pull request #212 from canjs/fix-qunit-ok
  • 4d07c86 Merge pull request #189 from canjs/dont-redefine-data
  • 34f0854 Replaced QUnit.ok with QUnit.equal
  • 34b8f5c Fixing the incorrect use of QUnit.ok
  • 18531dd Merge remote-tracking branch 'origin/master' into dont-redefine-data
  • e3c3858 Make tests work on all supported platforms, including unrelated IE issue
  • fbf76d1 fix jshint error
  • b2c10a8 fix jshint error
  • 9715a88 Add test to show that sealed objects are still not extensible
  • f023cbc Don't attempt to redefine _data or _computed on DefineMaps if they're already defined

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 🌴

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions