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

Version 0.51.1 of rollup was just published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.51.0
Type	devDependency

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

rollup 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

Commits

The new version differs by 5 commits.

d60f212 Update changelog
c483668 0.51.1
55424a0 Merge pull request #1704 from rollup/handle-empty-return-statements
2d9d29a Resolve #1702
d91cba0 Update changelog

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

Version 10.3.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.2.2
Type	devDependency

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

As nyc 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](https://travis-ci.org/arlac77/bocf/builds/227091295?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 4 commits ahead by 4, behind by 2.

55e826d chore(release): 10.3.0
89dc7a6 chore: explicit update of istanbul dependnecies (#562)
1887d1c feat: add support for --no-clean, to disable deleting raw coverage output (#558)
ff73b18 fix: source-maps were not being cached in the parent process when --all was being used (#556)

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

Version 0.47.3 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.47.2
Type	devDependency

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

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

6b94155 -> v0.47.3
586e255 Merge pull request #1551 from rollup/gh-1550
c364ec4 deshadow aliased imports (#1550)
1b48335 Merge pull request #1549 from alippai/patch-1
a1c19b8 Add appveyor NodeJS 8 builds
ae996b7 Add travis for NodeJS 8
3353338 check for process.hrtime, closes #1495

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

Version 7.1.0 of config-expander just got published.

Branch	Build failing 🚨
Dependency	config-expander
Current Version	7.0.3
Type	dependency

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

config-expander 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](https://travis-ci.org/arlac77/bocf/builds/225396031)

Release Notes

v7.1.0

7.1.0 (2017-04-24)

Bug Fixes

handle missing function arg declaration well (340cfe0b)
handle missing function arg declaration well (c8f3d4a2)
check for function arguments to (f770800c)

Features

function: check number of arguments (e47a2c71)

Commits

The new version differs by 8 commits0.

340cfe0 fix: handle missing function arg declaration well
c8f3d4a fix: handle missing function arg declaration well
f770800 fix: check for function arguments to
8a81667 Merge pull request #80 from arlac77/template-sync-1
d2ddae4 chore: update package.json from template
e47a2c7 feat(function): check number of arguments
1d9a658 test: add external const eval
0bd943f chore(dependencies): [email protected]

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

Version 10.2.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.1.2
Type	devDependency

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

As nyc 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 6 commits .

455619f chore(release): 10.2.0
95cc09a feat: upgrade to version of yargs with extend support (#541)
43535f9 chore: explicit update of istanbuljs dependencies (#535)
98ebdff feat: allow babel cache to be enabled (#517)
50adde4 feat: exclude the coverage/ folder by default 🚀 (#502)
6a59834 chore(package): update tap to version 10.0.0 (#507)

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 rollup-plugin-commonjs is breaking the build 🚨

Version 7.0.1 of rollup-plugin-commonjs just got published.

Branch	Build failing 🚨
Dependency	rollup-plugin-commonjs
Current Version	7.0.0
Type	devDependency

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

As rollup-plugin-commonjs 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/pr The Travis CI build failed Details

Commits

The new version differs by 9 commits .

b5e6825 remove npm-debug.log
7ef5401 -> v7.0.1
e653306 Merge branch 'master' of https://github.com/rollup/rollup-plugin-commonjs
f348771 Merge pull request #170 from MaartenX/patch-1
a44edd9 Fixed travis error
82e7a2a Fixed issue #168
5f6ff3d tidy up tests
6f1cb76 update deps and tests
899bdaf fix #156

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 rollup-plugin-commonjs is breaking the build 🚨

Version 8.1.0 of rollup-plugin-commonjs just got published.

Branch	Build failing 🚨
Dependency	rollup-plugin-commonjs
Current Version	8.0.2
Type	devDependency

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

As rollup-plugin-commonjs 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 12 commits.

f7602d9 -> v8.1.0
60846f5 Merge pull request #212 from rollup/external-from-commonjs
5309d9b update appveyor config
d4a14e3 lint
d81bca9 handle options.external correctly
a5718e2 Merge branch 'master' into external-from-commonjs
cb0f14e just test in node 8
078332b failing test for external module imported from commonjs
61157df Merge pull request #195 from calvinmetcalf/top-level-return
bcadeb1 Drop extra linebreak from tests (#205)
c831ca4 Include a regexp in options' documentation (#197)
bb3045d top level return support

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

Version 0.46.2 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.46.1
Type	devDependency

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

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

8e7cbe0 -> v0.46.2
4451ee2 Merge pull request #1537 from rollup/gh-1480
7a2a8d2 init rhs of for-in loop head with correct scope - fixes #1480
d0392e9 Merge pull request #1536 from rollup/gh-1533
a30f5a5 pass through all necessary options to bundle.write in rollup.watch (fixes #1533)
834acb3 get test to pass
bd39fa3 allow passing interop through cli - true/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 🌴

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

An in-range update of config-expander is breaking the build 🚨

Version 7.0.2 of config-expander just got published.

Branch	Build failing 🚨
Dependency	config-expander
Current Version	7.0.1
Type	dependency

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

As config-expander 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

v7.0.2

7.0.2 (2017-04-04)

Bug Fixes

package: merge package template from Kronos-Tools/npm-package-template (a0fc21e7)

Commits

The new version differs by 3 commits .

bd7c5d1 Merge pull request #78 from arlac77/template-sync-1
a0fc21e fix(package): merge package template from Kronos-Tools/npm-package-template
74521e5 chore(depenencies): [email protected] [email protected]

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

Version 7.0.1 of config-expander just got published.

Branch	Build failing 🚨
Dependency	config-expander
Current Version	7.0.0
Type	dependency

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

As config-expander 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/pr The Travis CI build failed Details

Release Notes

v7.0.1

7.0.1 (2017-03-09)

Bug Fixes

package: merge package template from Kronos-Tools/npm-package-template (8f928e7e)

Commits

The new version differs by 3 commits .

7c186bc docs(README): sync
03b66ac Merge pull request #77 from arlac77/template-sync-1
8f928e7 fix(package): merge package template from Kronos-Tools/npm-package-template

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 7.0.2 of semantic-release just got published.

Branch	Build failing 🚨
Dependency	semantic-release
Current Version	7.0.1
Type	devDependency

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

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

v7.0.2

7.0.2 (2017-08-16)

Bug Fixes

post: create v1.2.3 tag tag instead of branch (3f85597)

Note that if a version was released with v7.0.1, you will run into the ENOTINHISTORY error :( To recover, follow these steps:
1. Make sure you are on your main branch and pulled the latest changes from remote
2. Edit the package.json file, set "version" to what ever should have been released. As an example, let's say the new version number would be 1.2.3. Save the change
3. run npm publish to release the new version. Make sure to run any pre-publish tasks first if you have any
4. revert the changes
5. create a tag with git tag v1.2.3 (put in the same version as in step 2. Push the tag to GitHub with git push --tags
6. Manually create a release for the tag
This will fix the problem and everything will work automagically again from here on now.

Commits

The new version differs by 1 commits.

0c79a9b fix(post): create git tag properly

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 rollup-plugin-commonjs is breaking the build 🚨

Version 8.0.1 of rollup-plugin-commonjs just got published.

Branch	Build failing 🚨
Dependency	rollup-plugin-commonjs
Current Version	8.0.0
Type	devDependency

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

As rollup-plugin-commonjs 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 .

91fbafb -> v8.0.1
6b1542a Merge pull request #180 from rollup/gh-179
2cfe204 remove declarators within a var declration correctly (#179)

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 🌴

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

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

Version 11.2.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.1.0
Type	devDependency

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

As nyc 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 7 commits.

b2ff72d chore(release): 11.2.0
97b962e chore: explicit update of istanbul-lib-instrument (#662)
0dcceda feat: allow cwd to be configured see #620
0fc6d8f chore: add support for --cwd (#542) (#620)
658dba4 fix: remove excluded files from coverage before writing (#649)
dd40dc5 feat: add possibility to filter coverage-maps (#637)
fb3ab92 docs: add link to community slack (#639)

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

Version 11.1.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.0.3
Type	devDependency

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

As nyc 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 5 commits.

a3f033f chore(release): 11.1.0
a076951 chore: upgrade to latest version of istanbul-lib-instrument
8768afe feat: upgrade to version of spawn-wrap that supports .EXE (#626)
2d92501 chore: attempt to fix appveyor (#623)
bbadc1f feat: add support for per file coverage checking (#591)

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

Version 0.4.1 of caporal just got published.

Branch	Build failing 🚨
Dependency	caporal
Current Version	0.4.0
Type	dependency

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

As caporal 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 3 commits .

f600dd7 chore(release): 0.4.1
3864a81 docs(CHANGELOG): 0.4.1
e00932b fix(help): use console.log for help() instead of custom logger (#38)

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

Version 0.41.6 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.41.5
Type	devDependency

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

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

a96a923 -> v0.41.6
7c8c6ba Merge pull request #1337 from krisselden/fix-cache-loader-sourcemaps
d94d8c2 Fix cache losing originalSourceMap for loaders with sourcemaps
ae9eb5c diction
d286702 Merge pull request #1330 from rollup/documentation
5cafe1b license text
5a718a2 quick start commands

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

Version 7.1.2 of config-expander just got published.

Branch	Build failing 🚨
Dependency	config-expander
Current Version	7.1.1
Type	dependency

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

config-expander 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

v7.1.2

7.1.2 (2017-05-07)

Bug Fixes

depednencies: [email protected] (4b0e612f)

Commits

The new version differs by 9 commits0.

4b0e612 fix(depednencies): [email protected]
3f147c7 Merge pull request #85 from arlac77/template-sync-1
b14b3cf chore(devDependencies): add rollup-plugin-commonjs=^8.0.2 from template
2e08212 Merge pull request #84 from arlac77/greenkeeper/nyc-10.3.2
db4b666 chore(package): update nyc to version 10.3.2
662f64d Merge pull request #83 from arlac77/template-sync-1
38b0756 chore: update package.json from template
c408563 Merge pull request #82 from arlac77/template-sync-1
755740d chore: update package.json from template

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

Version 0.41.5 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.41.4
Type	devDependency

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

As 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/pr The Travis CI build failed Details

Commits

The new version differs by 29 commits .

c33f575 -> v0.41.5
c8a980a add test for #1317
05c44e5 Merge branch 'patch-2' of https://github.com/porsager/rollup into porsager-patch-2
d3c19ed outwit uglify, which now tries to inline stuff
1b0823a Merge branch 'logging-fix' of https://github.com/diervo/rollup into diervo-logging-fix
74a0d1b Merge pull request #1311 from kzc/1273
9929d1b Merge pull request #1255 from Comandeer/fix-babili
ae54071 Merge pull request #1287 from olsonpm/fix-warn-on-namespace-conflict
a6aa96e add a test
3d311f7 Merge branch 'fix-default-conflict' of https://github.com/olsonpm/rollup into olsonpm-fix-default-conflict
178b822 typo that affects docs
a345361 Merge branch 'master' of https://github.com/rollup/rollup
6d352d6 fix guide link
007c264 documentation
49ac9e2 documentation

There are 29 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 nyc is breaking the build 🚨

Version 11.2.1 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.2.0
Type	devDependency

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

As nyc 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.

87281f9 chore(release): 11.2.1
3bd1527 fix: create temp directory when --no-clean flag is set #663 (#664)
a10d478 fix: apply exclude logic before remapping coverage (#667)

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 rollup-plugin-node-resolve is breaking the build 🚨

Version 2.1.0 of rollup-plugin-node-resolve just got published.

Branch	Build failing 🚨
Dependency	rollup-plugin-node-resolve
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 rollup-plugin-node-resolve 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 20 commits .

7c616ef -> v2.1.0
68505d7 Merge branch 'master' of https://github.com/ma2ciek/rollup-plugin-node-resolve into ma2ciek-master
0907e30 Merge branch 'jonhartnett-master'
66cce4f finish test for #79
a3b61e3 update deps
96f266a add test for #79
cfd00b4 Merge branch 'master' of https://github.com/jonhartnett/rollup-plugin-node-resolve into jonhartnett-master
8977184 dont test in node 0.12
48d89a6 Merge branch 'master' into master
da8a40c convert spaces to tabs
48127ab Merge pull request #53 from rezzza/jail
911fb70 Remove testing on node v. 0.12 from Travis
ae2e3f3 Remove unnecessary destruction assignment
f105d25 Fix missing directories
c891cce Add fix to symlinked packages

There are 20 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 rollup-plugin-commonjs is breaking the build 🚨

Version 8.2.3 of rollup-plugin-commonjs was just published.

Branch	Build failing 🚨
Dependency	rollup-plugin-commonjs
Current Version	8.2.1
Type	devDependency

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

rollup-plugin-commonjs 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

Commits

The new version differs by 15 commits.

3724521 8.2.3
33ce531 8.2.2
8d53cca Merge pull request #233 from mbostock/fix-require-collision
7c14734 Remove apparently-unneeded file.
386a1e7 Add test for require collision.
93cedc2 Fix #232 - require collision.
419a912 Update dependencies
d3cd998 Merge pull request #241 from rollup/update-test-config
8efa096 Silence a few test warnings
77c4838 Merge pull request #230 from caleb531/duplicate-export-fix
6a3046e Merge pull request #229 from DenisCarriere/patch-1
83315ad Merge pull request #226 from marijnh/master
4dae460 Make unwrapExports only pick out default when it exists
e49819a Fix rollup/rollup#1637 (with tests)
a453bb4 Update README.md

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 rollup-plugin-commonjs is breaking the build 🚨

Version 8.2.6 of rollup-plugin-commonjs was just published.

Branch	Build failing 🚨
Dependency	rollup-plugin-commonjs
Current Version	8.2.5
Type	devDependency

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

rollup-plugin-commonjs 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

Commits

The new version differs by 3 commits.

e800b4c 8.2.6
779cd9e Merge pull request #253 from rollup/update-acorn
10e09cb Raise minimal acorn version to resolve #252

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

Version 0.50.1 of rollup was just published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.50.0
Type	devDependency

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

rollup 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

Commits

The new version differs by 10 commits.

e773b58 0.50.1
ed2c00e Merge pull request #1660 from mjprude/hotfix/readme-starter-update
8365bb1 Merge pull request #1695 from lukastaegert/do-not-exclude-pure-external-modules
c406f97 Resolve #1645
63d9ef6 Merge pull request #1670 from Andarist/enhancement/as-git-dep
59d801d Tweaked install/publish related scripts - enabled installing as dep directly from git
5e16429 Merge pull request #1650 from corneliusweig/treeshake-sequence-expression
e5eb0ea Add SequenceExpression AST node resolving #1649
7dd1baf Point Readme to up-to-date starter projects
ce0ceb8 Remove conditional expressions if they have no effect.

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

Version 0.43.1 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.43.0
Type	devDependency

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

As 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 28 commits.

6f3f349 -> v0.43.1
22a2cd9 Merge pull request #1477 from rollup/gh-1264
85b01a9 ugh you have got to be kidding me
9b30ff0 ugh node 4
328a327 gah, try now
b9c9e4b move weak to optionalDependencies, as it appears to fail on Travis CI
672fac4 merge master -> gh-1264
0b77142 add leak test on prepublish
dee8f85 add test for memory leak
70ad5df Merge branch 'closure-memory-leak' of https://github.com/dmitrage/rollup into gh-1470
c17f7ce merge master -> gh-1264
3237330 Merge pull request #1464 from FelixRilling/dependency-uglify
c026cb2 Merge pull request #1463 from diervo/amdOptionsFix
287cd43 update acorn
b26ac1d less cryptic error if entry module is external (#1264)

There are 28 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 rollup is breaking the build 🚨

Version 0.45.1 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.45.0
Type	devDependency

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

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

87c4733 -> v0.45.1
5e4cbdc Merge pull request #1489 from rollup/gh-1483
e099d8c remove weak from optionalDependencies

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 rollup-plugin-commonjs is breaking the build 🚨

Version 8.2.1 of rollup-plugin-commonjs just got published.

Branch	Build failing 🚨
Dependency	rollup-plugin-commonjs
Current Version	8.2.0
Type	devDependency

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

As rollup-plugin-commonjs 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.

90e3a82 -> v8.2.1
5f9b99c Merge pull request #222 from jharris4/magic-string-fix-warnings
e849856 fix warnings by changing last argument of magicString.overwrite from boolean to { storeName: boolean }

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

Version 0.46.1 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.46.0
Type	devDependency

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

As 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 19 commits.

8969272 -> v0.46.1
0d5669b Merge pull request #1529 from rollup/gh-1528
f9f389c Merge pull request #1531 from rollup/gh-1530
5d651a7 only ship .js files
b962cf6 separate node entry from browser entry
d8d5eec update config
e8da9f5 remove source-map-support
aa2b54b Merge pull request #1527 from rollup/tidy-up-tests
0015e05 about to lose my sense of humour
7cd8717 GODDAMMIT
75152bf almost there
b38632e AARGGHHHH
2c05caa please let this work
b9d0779 losing my goddamn mind over here
6eba4d1 wtf. why are these tests passing locally but not in ci

There are 19 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 semantic-release is breaking the build 🚨

Version 8.0.1 of semantic-release just got published.

Branch	Build failing 🚨
Dependency	semantic-release
Current Version	8.0.0
Type	devDependency

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

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

v8.0.1

8.0.1 (2017-09-18)

Bug Fixes

package: update @semantic-release/commit-analyzer to version 3.0.1 (8c44c31)
package: update @semantic-release/release-notes-generator to version 4.0.0 (dd60b46)

Commits

The new version differs by 4 commits.

8c44c31 fix(package): update @semantic-release/commit-analyzer to version 3.0.1
dd60b46 fix(package): update @semantic-release/release-notes-generator to version 4.0.0
88b5895 docs(README): update commit lint suggestion (#429)
1ceae83 docs(troubleshooting): initial version (#399)

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

Version 1.15.2 of tar-fs just got published.

Branch	Build failing 🚨
Dependency	tar-fs
Current Version	1.15.1
Type	dependency

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

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

b79d82a 1.15.2
c2af4b9 bump mkdirp to fix 62

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

Version 1.15.3 of tar-fs just got published.

Branch	Build failing 🚨
Dependency	tar-fs
Current Version	1.15.2
Type	dependency

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

tar-fs 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 2 commits.

4c89247 1.15.3
7e106bb Add more special characters for windows. (#63)

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

Version 0.45.2 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.45.1
Type	devDependency

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

As 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 12 commits.

b7a4edf -> v0.45.2
66a6e88 Merge branch 'master' of github.com:rollup/rollup
e1e0f5a Merge pull request #1487 from TheWeatherCompany/twc-master
2ff79f9 Merge pull request #1482 from Andarist/fix/cli-extend
3e38651 Merge pull request #1490 from rollup/rollup-watch-gh-54
3b2363f install rollup-watch as devDependency
e9ea331 separate resolvedIds from resolvedExternalIds
782967a update LICENSE
b00bc3c Undo package.json changes
2607d4e Change to use hasOwnProperty check vs in to prevent TypeError
1bc1ea4 Change package name to @twc/rollup
be94551 Fixed --extend flag not being passed correctly from the CLI arguments

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

Version 10.3.2 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.3.1
Type	devDependency

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

As nyc 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

✅ codeclimate no new or fixed issues Details,- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details,- ❌ continuous-integration/travis-ci/pr The Travis CI build failed Details

Commits

The new version differs by 2 commits0.

e062a86 chore(release): 10.3.2
213206f fix: we should not create a cache folder if cache is false (#567)

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 🌴

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

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

Version 8.1.1 of rollup-plugin-commonjs just got published.

Branch	Build failing 🚨
Dependency	rollup-plugin-commonjs
Current Version	8.1.0
Type	devDependency

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

As rollup-plugin-commonjs 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

✅ codeclimate All good! Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details
❌ continuous-integration/travis-ci/pr The Travis CI build failed Details

Commits

The new version differs by 3 commits.

2bb0f30 -> v8.1.1
f49028c update deps
66e07fd update rollup

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 rollup-plugin-commonjs is breaking the build 🚨

Version 8.2.5 of rollup-plugin-commonjs was just published.

Branch	Build failing 🚨
Dependency	rollup-plugin-commonjs
Current Version	8.2.4
Type	devDependency

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

rollup-plugin-commonjs 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 jsdoc-to-markdown is breaking the build 🚨

Version 3.0.1 of jsdoc-to-markdown was just published.

Branch	Build failing 🚨
Dependency	jsdoc-to-markdown
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.

jsdoc-to-markdown 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

Commits

The new version differs by 5 commits.

5303919 3.0.1
47dff26 update dev-deps
4d07b82 upgrade deps
b49b772 remove separators from API docs
a42bbed upgrade deps.. refresh API 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 nyc is breaking the build 🚨

Version 11.0.3 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.0.2
Type	devDependency

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

As nyc 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 4 commits.

e9fad9f docs: add note about tap-nyc to README (#614)
f86b0b1 chore(release): 11.0.3
923b062 fix: upgrade to spawn-wrap version that works with babel-register (#617)
b1eb4d6 fix: update help link to list of reporters (#601)

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

Version 0.47.5 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.47.4
Type	devDependency

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

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

9cfada0 -> v0.47.5
714ae2d Merge pull request #1558 from rollup/gh-1532
8ec3e0d use Promise.resolve in mapSequence, to ensure each item is thenable - fixes #1532

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

Version 0.19.1 of ava just got published.

Branch	Build failing 🚨
Dependency	ava
Current Version	0.19.0
Type	devDependency

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

As ava 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
❌ continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details

Release Notes

0.19.1

A bugfix release. See 0.19.0 for full release notes.

Prevent MaxListenersExceededWarning from being emitted if a test file contains more than 10 tests d27bc8f
Fix t.end() not being available in the TypeScript definition for callback tests bd81ef4
Fix t.context not being available in the Flow definition for beforeEach() and afterEach() hooks d169f0e

Commits

The new version differs by 5 commits .

4cc3403 0.19.1
d169f0e Fix context for beforeEach and afterEach hooks in Flow type definition file (#1344)
bd81ef4 Fix TypeScript definition for callback tests
6224f31 Set up regression testing for TypeScript
d27bc8f Avoid MaxListenersExceededWarning in Sequence

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 rollup-plugin-commonjs is breaking the build 🚨

Version 8.0.2 of rollup-plugin-commonjs just got published.

Branch	Build failing 🚨
Dependency	rollup-plugin-commonjs
Current Version	8.0.1
Type	devDependency

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

As rollup-plugin-commonjs 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 .

f71f57d -> v8.0.2
84b166b Merge pull request #182 from rollup/gh-181
9bf49e1 fix another var rewrite bug (#181)

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

Version 0.53.3 of rollup was just published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.53.2
Type	devDependency

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

rollup 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

Commits

The new version differs by 10 commits.

1ceb6bc 0.53.3
bd73067 Update changelog
bdd8438 Merge branch 'no-explicit-external-warnings' into release-0.53.3
9c32ad8 Merge branch 'guybedford-reexport-aliasing-bug' into release-0.53.3
e75a487 0.53.2
9922dbe Update changelog
713ea76 Removes errors when output options is an array.
9b5bc4e include fix
546a4aa failing test case
8ef29d8 disable unresolved import warnings when resolve explicitly returns false

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

Version 7.0.3 of config-expander just got published.

Branch	Build failing 🚨
Dependency	config-expander
Current Version	7.0.2
Type	dependency

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

As config-expander 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

v7.0.3

7.0.3 (2017-04-13)

Bug Fixes

package: merge package template from Kronos-Tools/npm-package-template (de753c8f)

Commits

The new version differs by 2 commits .

486107e Merge pull request #79 from arlac77/template-sync-1
de753c8 fix(package): merge package template from Kronos-Tools/npm-package-template

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 🌴

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

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

Version 1.0.3 of pump was just published.

Branch	Build failing 🚨
Dependency	pump
Current Version	1.0.2
Type	dependency

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

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

Commits

The new version differs by 2 commits.

28557d8 1.0.3
a430c27 avoid ERR_INVALID_ARG_TYPE error on Node.js >= 9 (#23)

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

Version 6.2.7 of config-expander just got published.

Branch	Build failing 🚨
Dependency	config-expander
Current Version	6.2.6
Type	dependency

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

As config-expander 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/pr The Travis CI build could not complete due to an error Details

Release Notes

v6.2.7

6.2.7 (2017-01-27)

Bug Fixes

package: merge package template from Kronos-Tools/npm-package-template (65301e52)

Commits

The new version differs by 4 commits .

2fde955 Merge pull request #72 from arlac77/template-sync-1
65301e5 fix(package): merge package template from Kronos-Tools/npm-package-template
19d7ad8 Merge pull request #71 from arlac77/greenkeeper/expression-expander-5.3.8
7ab6598 chore(package): update expression-expander to version 5.3.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 travis-deploy-once is breaking the build 🚨

Version 4.3.2 of travis-deploy-once was just published.

Branch	Build failing 🚨
Dependency	travis-deploy-once
Current Version	4.3.1
Type	devDependency

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

travis-deploy-once 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 passed Details
✅ coverage/coveralls First build on greenkeeper/travis-deploy-once-4.3.2 at 92.982% Details
✅ codeclimate All good! Details
❌ continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details
❌ codecov/project CI failed. Details
❌ codecov/patch CI failed. Details

Release Notes

v4.3.2

4.3.2 (2018-01-17)

Bug Fixes

package: update url-join to version 3.0.0 (27a31a8)

Commits

The new version differs by 3 commits.

27a31a8 fix(package): update url-join to version 3.0.0
ec664a1 ci: use Build Stages
70d6baa chore(package): update semantic-release to version 12.2.2

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

Version 0.51.2 of rollup was just published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.51.1
Type	devDependency

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

rollup 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

Commits

The new version differs by 4 commits.

1035774 0.51.2
b348284 Update changelog
91bbd1f Merge pull request #1712 from rollup/fix-1706
ab8636f Resolve #1706

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 🌴

arlac77 / bocf Goto Github PK

bocf's Introduction

Hi there 👋

bocf's People

Contributors

Watchers

bocf's Issues

Version 0.51.1 of rollup was just published.

Version 10.3.0 of nyc just got published.

Version 0.47.3 of rollup just got published.

Version 7.1.0 of config-expander just got published.

7.1.0 (2017-04-24)

Bug Fixes

Features

Version 10.2.0 of nyc just got published.

Version 7.0.1 of rollup-plugin-commonjs just got published.

Version 8.1.0 of rollup-plugin-commonjs just got published.

Version 0.46.2 of rollup just got published.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Version 7.0.2 of config-expander just got published.

7.0.2 (2017-04-04)

Bug Fixes

Version 7.0.1 of config-expander just got published.

7.0.1 (2017-03-09)

Bug Fixes

Version 7.0.2 of semantic-release just got published.

7.0.2 (2017-08-16)

Bug Fixes

Version 8.0.1 of rollup-plugin-commonjs just got published.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Version 11.2.0 of nyc just got published.

Version 11.1.0 of nyc just got published.

Version 0.4.1 of caporal just got published.

Version 0.41.6 of rollup just got published.

Version 7.1.2 of config-expander just got published.

7.1.2 (2017-05-07)

Bug Fixes

Version 0.41.5 of rollup just got published.

Version 11.2.1 of nyc just got published.

Version 2.1.0 of rollup-plugin-node-resolve just got published.

Version 8.2.3 of rollup-plugin-commonjs was just published.

Version 8.2.6 of rollup-plugin-commonjs was just published.

Version 0.50.1 of rollup was just published.

Version 0.43.1 of rollup just got published.

Version 0.45.1 of rollup just got published.

Version 8.2.1 of rollup-plugin-commonjs just got published.

Version 0.46.1 of rollup just got published.

Version 8.0.1 of semantic-release just got published.

8.0.1 (2017-09-18)

Bug Fixes

Version 1.15.2 of tar-fs just got published.

Version 1.15.3 of tar-fs just got published.

Version 0.45.2 of rollup just got published.

Version 10.3.2 of nyc just got published.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Version 8.1.1 of rollup-plugin-commonjs just got published.

Version 8.2.5 of rollup-plugin-commonjs was just published.

Version 3.0.1 of jsdoc-to-markdown was just published.

Version 11.0.3 of nyc just got published.

Version 0.47.5 of rollup just got published.

Version 0.19.1 of ava just got published.

Version 8.0.2 of rollup-plugin-commonjs just got published.

Version 0.53.3 of rollup was just published.

Version 7.0.3 of config-expander just got published.

7.0.3 (2017-04-13)

Bug Fixes

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Version 1.0.3 of pump was just published.

Version 6.2.7 of config-expander just got published.

6.2.7 (2017-01-27)

Bug Fixes

Version 4.3.2 of travis-deploy-once was just published.

4.3.2 (2018-01-17)

Bug Fixes

🚨 The automated release from the `master` branch failed. 🚨

🚨 The automated release from the `master` branch failed. 🚨

🚨 The automated release from the `master` branch failed. 🚨

🚨 The automated release from the `master` branch failed. 🚨

🚨 The automated release from the `master` branch failed. 🚨