The generator-ca from caapim

An in-range update of parse-github-url is breaking the build 🚨

Version 1.0.1 of parse-github-url was just published.

Branch	Build failing 🚨
Dependency	parse-github-url
Current Version	1.0.0
Type	dependency

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

parse-github-url is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

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

Commits

The new version differs by 5 commits.

4b88517 1.0.1
bd5041e upgrade devDependencies, run update
ec38e82 Merge pull request #11 from CookPete/master
12a5fe4 Return the correct host for git@ URLs
2afab62 1.0.0

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 failed 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 semantic-release is breaking the build 🚨

Version 6.3.6 of semantic-release just got published.

Branch	Build failing 🚨
Dependency	semantic-release
Current Version	6.3.5
Type	dependency

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

semantic-release 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

❌ clahub Not all contributors have signed the Contributor License Agreement. Details,- ✅ continuous-integration/travis-ci/push The Travis CI build passed Details,- ✅ codecov/patch Coverage not affected when comparing d913048...11a4cc3 Details,- ✅ codecov/project 100% remains the same compared to d913048 Details

Release Notes

v6.3.6

6.3.6 (2017-01-13)

Bug Fixes

package:
- update github to version 8.0.0 (afd6ab75)
- update nopt to version 4.0.0 (b10c8910)

Commits

The new version differs by 8 commits0.

af90de9 Merge pull request #355 from semantic-release/dep-updates
aa012b3 Merge branch 'greenkeeper/tap-9.0.0' into dep-updates
5724b19 Merge branch 'greenkeeper/github-8.0.0' into dep-updates
97a8e73 Merge branch 'caribou' into greenkeeper/nopt-4.0.0
51e12a3 docs(package): fix 'home' link
afd6ab7 fix(package): update github to version 8.0.0
f80e056 chore(package): update tap to version 9.0.0
b10c891 fix(package): update nopt to version 4.0.0

false

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 validate-commit-msg is breaking the build 🚨

Version 2.12.1 of validate-commit-msg just got published.

Branch	Build failing 🚨
Dependency	validate-commit-msg
Current Version	2.12.0
Type	dependency

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

As validate-commit-msg 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

❌ clahub Not all contributors have signed the Contributor License Agreement. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details

Release Notes

v2.12.1

2.12.1 (2017-04-04)

Bug Fixes

lib: getting .git from parent dir (#74) (e3a81f82)

Commits

The new version differs by 2 commits .

e3a81f8 fix(lib): getting .git from parent dir (#74)
a579a3d test(config): fix tests broken on windows (#73)

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

Version 2.6.2 of rimraf just got published.

Branch	Build failing 🚨
Dependency	rimraf
Current Version	2.6.1
Type	devDependency

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

As rimraf 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 2 commits.

79b933f v2.6.2
38b907f Fix #159, correct 0o666 chmod

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

Version 2.10.0 of commitizen was just published.

Branch	Build failing 🚨
Dependency	`commitizen`
Current Version	2.9.6
Type	dependency

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

commitizen is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

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

Release Notes

v2.10.0

2.10.0 (2018-05-24)

Bug Fixes

lodash Node Security warning (#482) (0023958e)
adapter: Don't print git root to stdout (#428) (d5e24245)
cli: Don't print error stack trace if git-cz failed (#436) (#437) (53719a42)

Features

strategies: respect the --allow-emtpy flag (#477) (495437c1)

Commits

The new version differs by 15 commits.

89300f5 Configure Renovate (#464)
0023958 fix: lodash Node Security warning (#482)
40d8dab Activating Open Collective (#468)
495437c feat(strategies): respect the --allow-emtpy flag (#477)
07b92bc docs: Fix Angular commit conventions link (#458)
53853fe chore(Update cz-conventional-changelog to 2.0.0): (#439)
d74b920 chore: add a project .editorconfig (#456)
f359d65 docs(readme): change deprecated adapter (#457)
4b32235 docs(contributing): Indentation usage and link to angular convention (#455)
de2459f Grammar and layout tweaks (#447)
f2f0453 docs($README): add related projects (#444)
53719a4 fix(cli): Don't print error stack trace if git-cz failed (#436) (#437)
2e283a3 docs($readme): add note about avoiding double calls to precommit (#433)
d5e2424 fix(adapter): Don't print git root to stdout (#428)
bc39af3 docs(readme): Fix incorrect spelling of "changelog" (#427)

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

Version 3.1.0 of yeoman-assert just got published.

Branch	Build failing 🚨
Dependency	yeoman-assert
Current Version	3.0.0
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 failed Details

Release Notes

v3.1.0

New assertion method assert.equalsFileContent() to asserts against exact file content.

Commits

The new version differs by 3 commits.

ae8dc73 3.1.0
62f3533 Adding assert.equalsFileContent (#24)
c45d328 ES2015ify and require Node.js 4

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 cz-conventional-changelog is breaking the build 🚨

Version 2.1.0 of cz-conventional-changelog was just published.

Branch	Build failing 🚨
Dependency	cz-conventional-changelog
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.

cz-conventional-changelog is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

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

Release Notes

v2.1.0

2.1.0 (2017-10-27)

Features

prompt: add confirmation fields + edit for clarity (#58) (d40ac2c5)

Commits

The new version differs by 3 commits.

d40ac2c feat(prompt): add confirmation fields + edit for clarity (#58)
f7a770e Merge pull request #57 from Epitrochoid/remove-unused-dep
2d1095b Removed unused pad-right dependency

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 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 failed 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.

3c83d8f 1.7.0
71ca3b3 Bump dependencies
ccbf848 Update dependencies to enable Greenkeeper 🌴 (#28)

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

Version 2.2.0 of codecov just got published.

Branch	Build failing 🚨
Dependency	codecov
Current Version	2.1.0
Type	dependency

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

codecov 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

❌ clahub Not all contributors have signed the Contributor License Agreement. Details,- ✅ continuous-integration/travis-ci/push The Travis CI build passed Details,- ✅ codecov/project 100% remains the same compared to d913048 Details,- ✅ codecov/patch Coverage not affected when comparing d913048...eaa3e57 Details

Release Notes

v2.2.0

Added: Support for Jenkins Blue Ocean
Added: Clear function to remove all discovered reports after uploading
Fix for Gitlab CI

Commits

The new version differs by 8 commits0.

7f8a29b v2.2.0
576b9fe add CI_REPOSITORY_URL to gitlab detection, fix #60
74a44f2 added -C to unlink reports after uploading
d1bf5e4 Merge pull request #56 from rochdev/blue-ocean
0a3cea3 Add support for Jenkins Blue Ocean
b365cd8 Merge pull request #57 from codecov/fix/cleanup
7f220cc Removing old execSync code from tests
4ba4609 v2.1.0

false

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

Version 4.17.5 of lodash was just published.

Branch	Build failing 🚨
Dependency	lodash
Current Version	4.17.4
Type	dependency

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

lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

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

Version 2.0.1 of eslint-config-ca just got published.

Branch	Build failing 🚨
Dependency	eslint-config-ca
Current Version	2.0.0
Type	devDependency

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

As eslint-config-ca 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

❌ clahub Not all contributors have signed the Contributor License Agreement. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ codecov/patch Coverage not affected when comparing d913048...df7d6a3 Details
✅ codecov/project 100% remains the same compared to d913048 Details

Release Notes

v2.0.1

2.0.1 (2017-04-07)

Bug Fixes

remove require-default-props rule in favour of Flowtype (cc4a79d1)

Commits

The new version differs by 5 commits .

98c3653 Merge pull request #14 from CAAPIM/require-default-props
cc4a79d fix: remove require-default-props rule in favour of Flowtype
9e5b3ce Merge pull request #12 from CAAPIM/greenkeeper/initial
a676eee docs(readme): add Greenkeeper badge
e8b124e chore(travis): whitelist greenkeeper branches

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 🌴

caapim / generator-ca Goto Github PK

generator-ca's People

Contributors

Stargazers

Watchers

generator-ca's Issues

Version 1.0.1 of parse-github-url was just published.

Version 2.0.1 of yosay just got published.

Commits

Version 6.3.6 of semantic-release just got published.

6.3.6 (2017-01-13)

Bug Fixes

Version 2.12.1 of validate-commit-msg just got published.

2.12.1 (2017-04-04)

Bug Fixes

Version 2.6.2 of rimraf just got published.

Version 2.10.0 of commitizen was just published.

2.10.0 (2018-05-24)

Bug Fixes

Features

Version 3.1.0 of yeoman-assert just got published.

Version 2.1.0 of cz-conventional-changelog was just published.

2.1.0 (2017-10-27)

Features

Version 1.7.0 of yeoman-test just got published.

Version 2.2.0 of codecov just got published.

Version 4.17.5 of lodash was just published.

Version 2.0.1 of eslint-config-ca just got published.

2.0.1 (2017-04-07)

Bug Fixes

Recommend Projects

Recommend Topics

Recommend Org