Giter VIP home page Giter VIP logo

yayp's People

Contributors

greenkeeper[bot] avatar greenkeeperio-bot avatar zozzz avatar

Watchers

avatar

yayp's Issues

An in-range update of @types/chai is breaking the build 🚨

Version 4.1.4 of @types/chai was just published.

Branch Build failing 🚨
Dependency @types/chai
Current Version 4.1.3
Type devDependency

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

@types/chai is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/jsdom is breaking the build 🚨

Version 11.0.5 of @types/jsdom was just published.

Branch Build failing 🚨
Dependency @types/jsdom
Current Version 11.0.4
Type devDependency

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

@types/jsdom is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of chai is breaking the build 🚨

Version 4.1.0 of chai just got published.

Branch Build failing 🚨
Dependency chai
Current Version 4.0.2
Type devDependency

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

As chai 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
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 4.1.0 / 2017-07-11

This release includes one new feature and a few bug fixes.

New Features

Bug Fixes

  • Allow dates for isBelow and isAbove assertions (#980, #990; @v1adko)
  • fix: check target's type in .property assertion (#992; @meeber)

Chores

Commits

The new version differs by 16 commits.

  • df9073c Merge pull request #998 from v1adko/make-release
  • cad9933 Merge pull request #1004 from chaijs/code-owners
  • cf70b11 Create CODEOWNERS
  • 3397dda Merge pull request #1005 from meeber/skip-failing-tests
  • 11a6f85 test: skip failing .include tests in IE11
  • 45cb327 [email protected]
  • 2eddd79 Add ES6 collection support to include() (#994)
  • 3c932e2 feat: allow dates for isBelow and isAbove assertions (#990)
  • 3bcb21c Merge pull request #979 from chaijs/greenkeeper/browserify-14.4.0
  • 5daceab Merge pull request #988 from samlanning/missing-var
  • 9116bc8 Merge pull request #993 from meeber/refactor-expect-types
  • 351e968 Merge pull request #992 from meeber/property-target-type
  • e7b2384 refactor: expectTypes to access ssfi flag
  • e6ddf64 fix: check target's type in .property assertion
  • 7e466af Add a missing var keyword found by lgtm.com

There are 16 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 🌴

An in-range update of gulp-typescript is breaking the build 🚨

Version 3.2.0 of gulp-typescript just got published.

Branch Build failing 🚨
Dependency gulp-typescript
Current Version 3.1.7
Type devDependency

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

As gulp-typescript 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
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes v3.2.0 - TSConfig Extends Support

This release adds support for the extends key in tsconfig files. Furthermore it adds compatibility with TypeScript 2.5-dev.

Commits

The new version differs by 13 commits.

  • 574ac44 Update release
  • d6d3c9f Version 3.2.0
  • ae4a2f9 Remove unused git submodules
  • bc1afb4 Tsconfig-extends cleanup
  • 6559ded Merge pull request #522 from weswigham/patch-1
  • 22167ad Allow TS 2.5 dev builds as a peer dependency version
  • a81178e Merge pull request #494 from lddubeau/experiment/support-extends
  • f43e9f5 Update release.
  • b379858 Add test cases for "extends".
  • 85065f6 Use object spread to shallow copy.
  • 0b791d6 File name fix.
  • bd63614 Let TypeScript do the copy.
  • 978498e Initial work on getting support for "extends".

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 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of merge2 is breaking the build 🚨

Version 1.1.0 of merge2 just got published.

Branch Build failing 🚨
Dependency merge2
Current Version 1.0.3
Type devDependency

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

As merge2 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
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 1 commits.

  • 9d0b0a4 use ES6, test in Node.js 8

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 🌴

An in-range update of @types/mocha is breaking the build 🚨

Version 5.2.2 of @types/mocha was just published.

Branch Build failing 🚨
Dependency @types/mocha
Current Version 5.2.1
Type devDependency

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

@types/mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of gulp-rollup is breaking the build 🚨

Version 2.14.0 of gulp-rollup just got published.

Branch Build failing 🚨
Dependency gulp-rollup
Current Version 2.13.0
Type devDependency

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

As gulp-rollup 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
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 3 commits.

  • 16c27c7 Merge pull request #60 from mcasimir/r45
  • ec8a25e 2.14.0
  • 7eecfab Updated Rollup to v0.45.x and updated code to work with new version

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 🌴

An in-range update of @types/node is breaking the build 🚨

Version 8.0.9 of @types/node just got published.

Branch Build failing 🚨
Dependency @types/node
Current Version 8.0.8
Type devDependency

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

As @types/node 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
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
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 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.