This version is covered by your current version range and after updating it in your project the build failed.
As can-connect 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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/canjs/react-view-model/builds/237979602?utm_source=github_status&utm_medium=notification)
Release NotesValidate behavior requirements
Behaviors that depend on properties of the underlying behaviors now check for the existence of these and raise meaningful errors at connection creation time if they're missing.
46be865Move production steal-removal of validate helper to individual usages
d8824d9Change can-validate-interface version string to '0.x' until we are ready to release a 1.0.0
e95f572Add required props to test stub behaviors added during most recent rebase
1dc4ee9cache-requests should throw error if cacheConnection is missing
a87b62eAdd missing 'List' prop expected by constructor-hydrate
0898debAdd interface validation helper. Update behaviors to use it. Update tests to have extra properties required to pass validations.
4f2eedcMerge pull request #260 from canjs/259-createInstance-buffer
2af4963Merge pull request #284 from canjs/270-real-time-set-warning
6e66a27Replace call to JSON.stringify() with can-util/js/dev/dev.stringify so that properties with a value of undefined show up in dev warnings. (e.g. canDev.stringify({ foo: undefined }) // "{ "foo": undefined }") Resolves #270
1868ab8Update realtime createInstance to wait until all createData promises are resolved
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 1.4.0 of can-connect just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As can-connect 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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/canjs/react-view-model/builds/237979602?utm_source=github_status&utm_medium=notification)Release Notes
Validate behavior requirementsBehaviors that depend on properties of the underlying behaviors now check for the existence of these and raise meaningful errors at connection creation time if they're missing.
#290
Commits
The new version differs by 15 commits.
c21176a
Update dist for release
a230fc0
Merge pull request #295 from canjs/can-connect-next
e96e41c
Merge pull request #294 from canjs/use-interface-validator
205772f
'behaviour' to 'behavior'
ae28ee2
Lighter custom error implementation
46be865
Move production steal-removal of validate helper to individual usages
d8824d9
Change can-validate-interface version string to '0.x' until we are ready to release a 1.0.0
e95f572
Add required props to test stub behaviors added during most recent rebase
1dc4ee9
cache-requests should throw error if cacheConnection is missing
a87b62e
Add missing 'List' prop expected by constructor-hydrate
0898deb
Add interface validation helper. Update behaviors to use it. Update tests to have extra properties required to pass validations.
4f2eedc
Merge pull request #260 from canjs/259-createInstance-buffer
2af4963
Merge pull request #284 from canjs/270-real-time-set-warning
6e66a27
Replace call to
JSON.stringify()
withcan-util/js/dev/dev.stringify
so that properties with a value ofundefined
show up in dev warnings. (e.g.canDev.stringify({ foo: undefined }) // "{ "foo": undefined }"
) Resolves #2701868ab8
Update realtime createInstance to wait until all createData promises are resolved
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: