Giter VIP home page Giter VIP logo

generator-starling's People

Contributors

gitter-badger avatar greenkeeper[bot] avatar zguillez avatar

Stargazers

 avatar  avatar

Watchers

 avatar

Forkers

gitter-badger

generator-starling's Issues

An in-range update of yeoman-test is breaking the build 🚨

Version 1.7.0 of yeoman-test just got published.

Branch Build failing 🚨
Dependency yeoman-test
Current Version 1.6.0
Type devDependency

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

As yeoman-test 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 could not complete due to an error Details

Release Notes v1.7.0
  • Update to yeoman-generator 1.x
  • Update to yeoman-environment 2.x
Commits

The new version differs by 3 commits.

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 grunt-contrib-watch is breaking the build 🚨

Version 1.0.1 of grunt-contrib-watch was just published.

Branch Build failing 🚨
Dependency grunt-contrib-watch
Current Version 1.0.0
Type devDependency

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

grunt-contrib-watch 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 could not complete due to an error Details

Commits

The new version differs by 16 commits.

There are 16 commits in total.

See the full diff

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 bower is breaking the build 🚨

Version 1.8.1 of bower just got published.

Branch Build failing 🚨
Dependency bower
Current Version 1.8.0
Type devDependency

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

As bower 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 could not complete due to an error 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 🌴

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

Version 1.2.0 of gulp-plumber was just published.

Branch Build failing 🚨
Dependency gulp-plumber
Current Version 1.1.0
Type devDependency

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

gulp-plumber 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 could not complete due to an error Details

Commits

The new version differs by 4 commits.

  • b91f934 1.2.0
  • c80d68e Merge pull request #54 from demurgos/issue-53
  • 310cd31 Drop dependency on deprecated gulp-util
  • ba3d6e4 improve errorHandler docs

See the full diff

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-istanbul is breaking the build 🚨

Version 1.1.2 of gulp-istanbul just got published.

Branch Build failing 🚨
Dependency gulp-istanbul
Current Version 1.1.1
Type devDependency

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

As gulp-istanbul 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 could not complete due to an error Details

Release Notes v1.1.2
  • Bump dependencies
Commits

The new version differs by 6 commits.

  • 502855e 1.1.2
  • ac8f966 Add documentation for reportOpts and watermarks (#121)
  • be326d1 Update README.md to warn about gulp-mocha (#120)
  • b0149ac fix(package): update istanbul-threshold-checker to version 0.2.1 (#112)
  • 7ec737a chore(package): update dependencies (#110)
  • b047c82 Update .travis.yml

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

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 yeoman-assert is breaking the build 🚨

Version 2.2.3 of yeoman-assert just got published.

Branch Build failing 🚨
Dependency yeoman-assert
Current Version 2.2.2
Type devDependency

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

As yeoman-assert 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 could not complete due to an error Details
Commits

The new version differs by 5 commits .

  • fa51fc5 2.2.3
  • 7d2945b Add eslint as dev dependency
  • 446ff2d Remove last dependency by es6-ing a line of code
  • 69639ae reduce dependencies and code complexity (#20)
  • 41b7f28 Update dependencies to enable Greenkeeper 🌴 (#22)

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 yeoman-generator is breaking the build 🚨

Version 1.1.1 of yeoman-generator just got published.

Branch Build failing 🚨
Dependency yeoman-generator
Current Version 1.1.0
Type dependency

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

As yeoman-generator 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 could not complete due to an error Details
Commits

The new version differs by 11 commits .

  • 80863b0 1.1.1
  • af3048f Fix issue with API documentation deploy script
  • 74cb46f Document legacy Generator.extend method properly - rel #996
  • 6d267f0 Use XO
  • 17173a2 chore(package): update yeoman-assert to version 3.0.0 (#1004)
  • 59d0120 Add eslint as direct dev dependency
  • cf67f66 Bump dependencies
  • ac542ba Bump dev dependencies
  • 0b06786 Improve option name validation message
  • 67b90f4 Add failing test for Boolean options starting with no-
  • 51414c0 Update Travis test matrix

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-exclude-gitignore is breaking the build 🚨

Version 1.2.0 of gulp-exclude-gitignore just got published.

Branch Build failing 🚨
Dependency gulp-exclude-gitignore
Current Version 1.1.1
Type devDependency

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

As gulp-exclude-gitignore 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 could not complete due to an error Details

Release Notes v1.2.0

Correctly ignore dotfiles when specified in .gitignore

Commits

The new version differs by 5 commits.

  • 248b91a Update sinon to the latest version 🚀 (#13)
  • 802bfc3 chore(package): update eslint-config-xo-space to version 0.16.0 (#10)
  • 533d5e0 chore(package): update sinon to version 2.0.0 (#9)
  • 7844c50 1.2.0
  • cca661f (Fix) Always match dotfiles in .gitignore

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-line-ending-corrector is breaking the build 🚨

Version 1.0.2 of gulp-line-ending-corrector was just published.

Branch Build failing 🚨
Dependency gulp-line-ending-corrector
Current Version 1.0.1
Type devDependency

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

gulp-line-ending-corrector 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 could not complete due to an error Details

Commits

The new version differs by 2 commits.

  • 5d4e0f1 Merge pull request #1 from JonahAcquah/master
  • 2ce8aa1 Upgraded coffeescript and line-ending-corrector references

See the full diff

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 grunt is breaking the build 🚨

Version 1.0.2 of grunt was just published.

Branch Build failing 🚨
Dependency grunt
Current Version 1.0.1
Type devDependency

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

grunt 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 could not complete due to an error Details

Commits

The new version differs by 27 commits.

  • ccc3163 v1.0.2
  • e7795dc Remove iojs from test matrix (#1622)
  • a6a133b Remove deprecation warning for coffeescript (#1621) r=@vladikoff
  • 06b377e https links to webchat.freenode.net and gruntjs.com (#1610)
  • 7c5242f Use node executable for local grunt bin for Windows support
  • f6cbb63 Oh right, Windows isnt bash
  • a9a20da Try and debug why appveyor is failing on npm
  • 48bba6c Move to the test script to avoid npm was unexpected at this time.
  • 6b97ac0 Try to fix appveyor script
  • 19003ba For appveyor, check node version to decide whether to install npm@3
  • 3fcf921 Install npm@3 if npm version is npm 1 or 2
  • 77fc157 Use the local version of grunt to run tests
  • 400601a Updating devDependencies
  • 6592ad1 Update travis/appveyor to node versions we support
  • b63aeec Dont manually install npm, use the version each node version corresponds with

There are 27 commits in total.

See the full diff

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 yosay is breaking the build 🚨

Version 2.0.1 of yosay just got published.

Branch Build failing 🚨
Dependency yosay
Current Version 2.0.0
Type dependency

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

yosay 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 could not complete due to an error Details

Release Notes 2.0.1 - Intergovernmental Authority of development

Ships a bugfix regarding colors …

Commits

72d685f - Set charIndex correctly when sentence contains whitespace (#30)

Commits

The new version differs by 2 commits.

  • 6c3028e 2.0.1
  • 72d685f Set charIndex correctly when sentence contains whitespace (#30)

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 eslint is breaking the build 🚨

Version 3.16.1 of eslint just got published.

Branch Build failing 🚨
Dependency eslint
Current Version 3.16.0
Type devDependency

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

As eslint 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 could not complete due to an error Details
Release Notes v3.16.1
  • ff8a80c Fix: duplicated autofix output for inverted fix ranges (fixes #8116) (#8117) (Teddy Katz)
  • a421897 Docs: fix typo in arrow-parens.md (#8132) (Will Chen)
  • 22d7fbf Chore: fix invalid redeclared variables in tests (#8130) (Teddy Katz)
  • 8d95598 Chore: fix output assertion typos in rule tests (#8129) (Teddy Katz)
  • 9fa2559 Docs: Add missing quotes in key-spacing rule (#8121) (Glenn Reyes)
  • f3a6ced Build: package.json update for eslint-config-eslint release (ESLint Jenkins)
Commits

The new version differs by 8 commits .

  • 589ab67 3.16.1
  • 4fec5b2 Build: package.json and changelog update for 3.16.1
  • ff8a80c Fix: duplicated autofix output for inverted fix ranges (fixes #8116) (#8117)
  • a421897 Docs: fix typo in arrow-parens.md (#8132)
  • 22d7fbf Chore: fix invalid redeclared variables in tests (#8130)
  • 8d95598 Chore: fix output assertion typos in rule tests (#8129)
  • 9fa2559 Docs: Add missing quotes in key-spacing rule (#8121)
  • f3a6ced Build: package.json update for eslint-config-eslint release

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 🌴

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.