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

✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 1 failing file. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/rollup-0.41.6 at 100.0% 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 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

✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 2 failing files. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/rollup-0.45.1 at 97.458% Details
✅ codecov/project 97.45% remains the same compared to 93e61e2 Details
✅ codecov/patch Coverage not affected when comparing 93e61e2...db42f49 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 is breaking the build 🚨

Version 0.41.4 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.41.3
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/gitbook/mobi GitBook build "mobi" is pending Details
❌ continuous-integration/gitbook/pdf GitBook build "pdf" is pending Details
❌ continuous-integration/gitbook/epub GitBook build "epub" is pending Details
✅ continuous-integration/gitbook/json GitBook build "json" succeeded Details
✅ continuous-integration/gitbook/website GitBook build "website" succeeded Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 1 failing file. Details

Commits

The new version differs by 5 commits .

80da8ec -> v0.41.4
23d50f6 Merge pull request #1262 from rollup/gh-1257
5c88259 handle call expressions of uncallable things more gracefully (#1257)
9c58833 Merge pull request #1261 from rollup/gh-1252
457be9c handle multiple export * from external declarations (#1252)

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 travis-deploy-once is breaking the build 🚨

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

Branch	Build failing 🚨
Dependency	travis-deploy-once
Current Version	4.3.2
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 failed Details
❌ continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details

Release Notes

v4.3.3

4.3.3 (2018-01-23)

Bug Fixes

package: update yargs to version 11.0.0 (cf1c97c)

Commits

The new version differs by 1 commits.

cf1c97c fix(package): update yargs to version 11.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 semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from `15.13.16` to `15.13.17`.

🚨 View failing branch.

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

semantic-release 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).
❌ codecov/project: 99.26% (-0.13%) compared to 28900e8 (Details).
✅ codecov/patch: Coverage not affected when comparing 28900e8...e662445 (Details).

Release Notes for v15.13.17

15.13.17 (2019-06-25)

Bug Fixes

package: update execa to version 2.0.0 (52c48be)

Commits

The new version differs by 2 commits.

01a0b2d test: use regexp to check missing module message
52c48be fix(package): update execa to version 2.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 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

✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 2 failing files. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/nyc-11.0.3 at 97.458% Details
✅ codecov/patch Coverage not affected when comparing c9abac9...d85728f Details
✅ codecov/project 97.45% remains the same compared to c9abac9 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.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

❌ bitHound - Code 2 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/rollup-0.43.1 at 97.458% Details
✅ codecov/patch Coverage not affected when comparing 94678ca...7660c23 Details
✅ codecov/project 97.45% remains the same compared to 94678ca 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 mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.3.0
Type	devDependency

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

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

✅ bitHound - Dependencies No failing dependencies. Details,- ❌ bitHound - Code 1 failing file. Details,- ✅ continuous-integration/travis-ci/push The Travis CI build passed Details,- ✅ security/snyk No new vulnerabilities Details,- ✅ codeclimate no new or fixed issues Details,- ✅ continuous-integration/travis-ci/pr The Travis CI build passed Details,- ✅ coverage/coveralls Coverage remained the same at 100.0% Details

Release Notes

v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

allowUncaught added to commandline as --allow-uncaught (and bugfixed)
warning-related Node flags

🎉 Enhancements

#2793, #2697: add --allowUncaught to Node.js (@lrowe)
#2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

#2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

#2778: Add license report and scan status (@xizhao)
#2794: no special case for macOS running Karma locally (@boneskull)
#2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

The new version differs by 9 commits0.

7554b31 Add Changelog for v3.4.0
9f7f7ed Add --trace-warnings flag
92561c8 Add --no-warnings flag
ceee976 lint test/integration/fixtures/simple-reporter.js
dcfc094 Revert "use semistandard directly"
93392dd no special case for macOS running Karma locally
4d1d91d --allow-uncaught cli option
fb1e083 fix allowUncaught in browser
4ed3fc5 Add license report and scan status

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.54.1 of rollup was just published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.54.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

❌ coverage/coveralls Coverage pending from Coveralls.io 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.

4bd7a0a 0.54.1
77e3b44 Update changelog
74de841 Merge pull request #1871 from KingHenne/more-ts-fixes
b413df4 Fix two more ts compiler errors based on emitted d.ts files

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.47.1 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.47.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

✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 2 failing files. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/rollup-0.47.1 at 97.458% Details
✅ codecov/patch Coverage not affected when comparing da8aec6...854c386 Details
✅ codecov/project 97.45% remains the same compared to da8aec6 Details

Commits

The new version differs by 6 commits.

be426f4 -> v0.47.1
08a4ed5 Merge branch 'master' of github.com:rollup/rollup
1ccf54d Merge pull request #1548 from rollup/gh-1547
a61e61b squelch warning from chalk
f85ffe8 ignore external namespace imports when deshadowing - fixes #1547
3c1b2ff update dependencies, lint

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 15.9.8 of semantic-release was just published.

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

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

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

Release Notes

v15.9.8

15.9.8 (2018-08-10)

Bug Fixes

package: update get-stream to version 4.0.0 (e882096)

Commits

The new version differs by 1 commits.

e882096 fix(package): update get-stream to version 4.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 rollup is breaking the build 🚨

Version 0.39.1 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.39.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/gitbook/pdf GitBook build "pdf" is pending Details
❌ bitHound - Code 1 failing file. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/gitbook/json GitBook build "json" succeeded Details
✅ continuous-integration/gitbook/website GitBook build "website" succeeded Details
✅ continuous-integration/gitbook/mobi GitBook build "mobi" succeeded Details
✅ continuous-integration/gitbook/epub GitBook build "epub" succeeded Details

Commits

The new version differs by 8 commits .

415985b -> v0.39.1
38bb9d9 Merge pull request #1204 from rollup/gh-1198
d1d667f ignore var inits in dead branches - fixes #1198
11a2830 Merge pull request #1202 from rollup/gh-1082
532dff1 change recommendation to local installation of rollup-watch (#1082)
c597b91 Merge pull request #1200 from rollup/gh-1197
708fb98 warn on missing format (fixes #1197)
979cfc2 update a few dependencies

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

Version 0.41.3 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.41.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/gitbook/mobi GitBook build "mobi" is pending Details
❌ continuous-integration/gitbook/pdf GitBook build "pdf" is pending Details
✅ continuous-integration/gitbook/json GitBook build "json" succeeded Details
✅ continuous-integration/gitbook/website GitBook build "website" succeeded Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 1 failing file. Details
✅ continuous-integration/gitbook/epub GitBook build "epub" succeeded Details

Commits

The new version differs by 3 commits .

4bbf9fd -> v0.41.3
603d2e7 Merge pull request #1260 from rollup/gh-1258
3a8b1c1 dont treat this.foo as possible namespace - fixes #1258

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

The devDependency semantic-release was updated from `15.13.20` to `15.13.21`.

🚨 View failing branch.

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

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

Release Notes for v15.13.21

15.13.21 (2019-08-12)

Bug Fixes

package: update hosted-git-info to version 3.0.0 (391af98)

Commits

The new version differs by 3 commits.

391af98 fix(package): update hosted-git-info to version 3.0.0
d45d8b6 docs: fix typo
519df0d chore: remove commitizen from our dependencies

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.46.3 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.46.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

❌ bitHound - Code 2 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/rollup-0.46.3 at 97.458% Details
✅ codecov/patch Coverage not affected when comparing 909faa2...935d734 Details
✅ codecov/project 97.45% remains the same compared to 909faa2 Details

Commits

The new version differs by 13 commits.

b7e1d49 -> v0.46.3
55b2e46 install console-group for debugging convenience
c6af5c9 Merge pull request #1542 from rollup/gh-1538
f8f2fa7 init for loop scopes correctly
5dec01d Merge pull request #1541 from rollup/gh-1488
0e5f8b6 deshadow indirectly-imported namespaces (#1488)
2e76960 Merge branch 'master' of github.com:rollup/rollup
e70dad3 Merge pull request #1540 from rollup/gh-1511
a44f442 lint
483dc69 use source-map-support in development
cc0e5c7 dont include empty imports for reexported external modules
671757e treat reexports differently from exports
6ba6440 fix external namespace imports in es output (#1511)

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

❌ bitHound - Code 2 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/rollup-0.47.5 at 97.458% Details
✅ codecov/patch Coverage not affected when comparing b90d86d...1fcb055 Details
✅ codecov/project 97.45% remains the same compared to b90d86d 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 🌴

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.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

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

Version 3.4.2 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.4.1
Type	devDependency

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

As mocha 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 passed Details
❌ bitHound - Code 1 failing file. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ security/snyk No new vulnerabilities Details
✅ codeclimate no new or fixed issues Details
✅ continuous-integration/travis-ci/pr The Travis CI build passed Details
✅ coverage/coveralls Coverage remained the same at 100.0% Details

Release Notes

fake-success

3.4.2 / 2017-05-24

🐛 Fixes

#2802: Remove call to deprecated os.tmpDir (@makepanic)
#2820: Eagerly set process.exitCode (@chrisleck)

🔩 Other

#2778: Move linting into an npm script (@Munter)

Commits

The new version differs by 7 commits.

a15b20a :ship: Release v3.4.2
fc802a9 :memo: Add Changelog for v3.4.2
10ff0ec Eagerly set process.exitCode (#2820)
fc35691 Merge pull request #2818 from makepanic/issue/2802
3e7152f Remove call to deprecated os.tmpDir (#2802)
e249434 Merge pull request #2807 from mochajs/npm-script-lint
17a1770 Move linting into an npm script. Relates to #2805

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 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.56.4 of rollup was just published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.56.3
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 could not complete due to an error Details

Commits

The new version differs by 38 commits.

018bcd2 0.56.4
a7627e3 Merge branch 'release-0.56.4'
58a6da4 Reset git on postcommit to fix a webstorm issue
65dd2d1 Merge branch 'asmockler-prettier' into release-0.56.4
77079db Merge branch 'system-form' into release-0.56.4
53003b8 Merge branch 'lamby-reproducible-build' into release-0.56.4
9291989 Merge branch 'reexport-tracing' into release-0.56.4
c3da6aa Merge branch 'chunk-import-variable-deduping' into release-0.56.4
e932f95 Merge branch 'throw-on-warnings' into release-0.56.4
3f74e82 Merge branch 'system-default-formatting' into release-0.56.4
8c56d63 Merge branch 'adrianheine-sourcemap' into release-0.56.4
dfc3280 0.56.3
8865311 Make sure tests are only removed if they contain at most an "_actual" directory
fa7a618 Automatically remove directories of missing tests instead of throwing an error
ccd9d23 getModuleDeclarations refactoring

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

Ability to register new UTIs

Would this package be likely to adopt the ability to register openers for UTIs or URIs?

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

The devDependency esm was updated from `3.0.84` to `3.1.0`.

🚨 View failing branch.

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

esm 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).
❌ codecov/project: 97.16% (-0.6%) compared to 44616fe (Details).
✅ codecov/patch: Coverage not affected when comparing 44616fe...f4e8758 (Details).
✅ coverage/coveralls: First build on greenkeeper/esm-3.1.0 at 98.659% (Details).

Commits

The new version differs by 424 commits.

33ee0ac Bump to v3.1.0.
a84a624 Update deps.
9110dd2 Cleanup readme.
7adc4fd Make Package exposable through require().
c149647 Newline nit.
885afd0 Add circular entry to esm loader fake compile data.
c7a5a1f Update getNativeSource() for latest Node master branch.
8a3d1ce Remove unneeded catch param.
8e8c354 Add more entry and package cache guards to env modules.
b77cf1a Don't cache entry or package instances in isSideloaded().
f326152 Fix wasm support regression.
fd47bfc Reset entry validation for repl.
7869529 Remove validation dead code from vm hook for now.
6ac3788 Cleanup done() handler.
34c0624 Avoid multi-var assignments.

There are 250 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 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

✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 2 failing files. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/rollup-0.47.3 at 97.458% Details
✅ codecov/patch Coverage not affected when comparing fd65b43...a9d52d1 Details
✅ codecov/project 97.45% remains the same compared to fd65b43 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 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

❌ bitHound - Code 2 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/nyc-11.1.0 at 97.458% Details
✅ codecov/project 97.45% remains the same compared to 3ddcf97 Details
✅ codecov/patch Coverage not affected when comparing 3ddcf97...5a4af1e 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 rollup is breaking the build 🚨

Version 0.60.1 of rollup was just published.

Branch	Build failing 🚨
Dependency	`rollup`
Current Version	0.60.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 could not complete due to an error Details

Commits

The new version differs by 7 commits.

264c867 0.60.1
d1b13f2 Merge branch 'large-var-count'
647460f Merge branch 'ongenerate-fix'
fbde57e fix input validation after options hook
b0eda7c include fix for chunkId closure
2b0b6c9 fix ongenerate signature regression
662ee81 fix large variable count numbering

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

Version 3.3.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.2.0
Type	devDependency

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

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

- ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/arlac77/uti/3ed56d34de678a8854c8abe5add0aed0e5268787/dependencies/npm?status=passing),- ❌ **bitHound - Code** 1 failing file. [Details](https://www.bithound.io/github/arlac77/uti/3ed56d34de678a8854c8abe5add0aed0e5268787/files#filter-failing-file),- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/arlac77/uti/builds/225155755),- ✅ **coverage/coveralls** First build on greenkeeper/mocha-3.3.0 at 100.0% [Details](https://coveralls.io/builds/11209802)

Release Notes

coverave

Thanks to all our contributors, maintainers, sponsors, and users! ❤️

As highlights:

We've got coverage now!
Testing is looking less flaky \o/.
No more nitpicking about "mocha.js" build on PRs.

🎉 Enhancements

#2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
#2769: Support --inspect-brk on command-line (@igwejk)

🐛 Fixes

#2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)

🔍 Coverage

#2672: Add coverage for node tests (@c089, @Munter)
#2680: Increase tests coverage for base reporter (@epallerols)
#2690: Increase tests coverage for doc reporter (@craigtaub)
#2701: Increase tests coverage for landing, min, tap and list reporters (@craigtaub)
#2691: Increase tests coverage for spec + dot reporters (@craigtaub)
#2698: Increase tests coverage for xunit reporter (@craigtaub)
#2699: Increase tests coverage for json-stream, markdown and progress reporters (@craigtaub)
#2703: Cover .some() function in utils.js with tests (@seppevs)
#2773: Add tests for loading reporters w/ relative/absolute paths (@sul4bh)

🔩 Other

Remove bin/.eslintrc; ensure execs are linted (@boneskull)
#2542: Expand CONTRIBUTING.md (@boneskull)
#2660: Double timeouts on integration tests (@Munter)
#2653: Update copyright year ([@Scottkao85], @Munter)
#2621: Update dependencies to enable Greenkeeper (@boneskull, @greenkeeper)
#2625: Use trusty container in travis-ci; use "artifacts" addon (@boneskull)
#2670: doc(CONTRIBUTING): fix link to org members (@coderbyheart)
Add Mocha propaganda to README.md (@boneskull)
#2470: Avoid test flake in "delay" test (@boneskull)
#2675: Limit browser concurrency on sauce (@boneskull)
#2669: Use temporary test-only build of mocha.js for browsers tests (@Munter)
Fix "projects" link in README.md (@boneskull)
#2678: Chore(Saucelabs): test on IE9, IE10 and IE11 (@coderbyheart)
#2648: Use semistandard directly (@kt3k)
#2727: Make the build reproducible (@lamby)

Commits

The new version differs by 89 commits0.

fb1687e :ship: Release v3.3.0
1943e02 Add Changelog for v3.3.0
861e968 Refactor literal play-icon hex code to a var
1d3c5bc Fix typo in karma.conf.js
9bd9389 Fix spec paths in test HTML files
0a93024 Adds tests for loading reporters w/ relative/absolute paths (#2773)
73929ad Comment special treatment of '+' in URL query parsing
e2c9514 Merge pull request #2769 from igwejk/support_inspect_break_in_opts
038c636 Support --inspect-brk on command-line
b4ebabd Merge pull request #2727 from lamby/reproducible-build
882347b Please make the build reproducible.
a2fc76c Merge pull request #2703 from seppevs/cover_utils_some_fn_with_tests
ed61cd0 cover .some() function in utils.js with tests
f42cbf4 Merge pull request #2701 from craigtaub/landingSpec
6065242 use stubbed symbol

There are 89 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 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

- ❌ **bitHound - Code** 1 failing file. [Details](https://www.bithound.io/github/arlac77/uti/8a6cf200ac08f9cbd3a7ee730440f5993c7228e4/files#filter-failing-file),- ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/arlac77/uti/8a6cf200ac08f9cbd3a7ee730440f5993c7228e4/dependencies/npm?status=passing),- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/arlac77/uti/builds/227082383?utm_source=github_status&utm_medium=notification),- ✅ **coverage/coveralls** First build on greenkeeper/nyc-10.3.0 at 100.0% [Details](https://coveralls.io/builds/11301304)

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

Version 10.1.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.0.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/gitbook/pdf GitBook build "pdf" is pending Details
❌ continuous-integration/gitbook/mobi GitBook build "mobi" is pending Details
❌ continuous-integration/gitbook/epub GitBook build "epub" is pending Details
✅ continuous-integration/gitbook/json GitBook build "json" succeeded Details
❌ bitHound - Code 1 failing file. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/gitbook/website GitBook build "website" succeeded Details

Commits

The new version differs by 14 commits .

8f7af3a chore(release): 10.1.0
8c58d68 fix: address edge-cases related to --all when instrumentation is disabled (#482)
8b58c05 feat: allow eager instantiation of instrumenter (#490)
d8d2de0 feat: upgrade to istanbul-lib-instrument with support for 'const foo = function () {}' name preservation. upgrade to istanbul-lib-hook with fix for ts-node. (#494)
7708235 chore: add test and docs for high and low watermarks (#493)
0a1d72a feat: reporting watermarks can now be set in nyc config stanza (#469)
1022b16 fix: pass configuration options to --check-coverage (#483)
7b4c090 chore(package): update tap to version 9.0.3 (#488)
093963b chore(release): 10.0.2
e01ec8c fix: upgrade to newer istanbul-lib-instrument, with fixes for inferred function names (#479)
2e39e00 chore(release): 10.0.1
e0ef1d5 fix: upgrade spawn-wrap and istanbul-lib-instrument (#477)
8603aa9 chore(package): update is-windows to version 1.0.0 (#466)
64ae4f3 chore(package): update standard-version to version 4.0.0 (#461)

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.40.1 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.40.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/gitbook/pdf GitBook build "pdf" is pending Details
❌ continuous-integration/gitbook/epub GitBook build "epub" is pending Details
✅ continuous-integration/gitbook/json GitBook build "json" succeeded Details
✅ continuous-integration/gitbook/website GitBook build "website" succeeded Details
❌ bitHound - Code 1 failing file. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/gitbook/mobi GitBook build "mobi" succeeded Details

Commits

The new version differs by 3 commits .

6cf998a -> v0.40.1
7af9387 Merge pull request #1218 from rollup/export-default-no-space
e7fa75c handle export default{}

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.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

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

Version 0.60.7 of rollup was just published.

Branch	Build failing 🚨
Dependency	`rollup`
Current Version	0.60.6
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 3 commits.

6e00418 0.60.7
853bb2d Merge branch 'dmitrage-transform-hook-typings'
c071d56 Use primitive string type in TransformHook

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

✅ security/snyk No new vulnerabilities Details
✅ codeclimate All good! Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 2 failing files. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ continuous-integration/travis-ci/pr The Travis CI build passed Details
✅ coverage/coveralls Coverage remained the same at 97.458% Details
✅ codecov/project 97.45% remains the same compared to 492b9da Details
✅ codecov/patch Coverage not affected when comparing 492b9da...2d07e8e 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.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

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

❌ bitHound - Code 2 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/rollup-0.45.2 at 97.458% Details
✅ security/snyk No new vulnerabilities Details
✅ codeclimate All good! Details
✅ continuous-integration/travis-ci/pr The Travis CI build passed Details
✅ codecov/project 97.45% remains the same compared to f659eea Details
✅ codecov/patch Coverage not affected when comparing f659eea...ce82075 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 🌴

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

❌ bitHound - Code 1 failing file. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/rollup-0.41.5 at 100.0% 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 🌴

refactor away initialize() and only user a Promise

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

❌ bitHound - Code 1 failing file. Details,- ✅ bitHound - Dependencies No failing dependencies. Details,- ✅ security/snyk No new vulnerabilities Details,- ✅ codeclimate no new or fixed issues Details,- ✅ continuous-integration/travis-ci/push The Travis CI build passed Details,- ✅ continuous-integration/travis-ci/pr The Travis CI build passed Details,- ✅ coverage/coveralls Coverage remained the same at 100.0% 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 🌴

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

Version 0.39.2 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.39.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/gitbook/epub GitBook build "epub" is pending Details
❌ continuous-integration/gitbook/mobi GitBook build "mobi" is pending Details
✅ continuous-integration/gitbook/json GitBook build "json" succeeded Details
✅ continuous-integration/gitbook/website GitBook build "website" succeeded Details
❌ continuous-integration/gitbook/pdf GitBook build "pdf" failed Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 1 failing file. Details

Commits

The new version differs by 3 commits .

a00d391 -> v0.39.2
04dbe12 Merge pull request #1205 from rollup/gh-1153
595fa58 prevent mutation of cached ASTs (#1153)

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.37.1 of rollup just got published.

Branch	Build failing 🚨
Dependency	rollup
Current Version	0.37.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/gitbook/pdf GitBook build "pdf" is pending Details
❌ continuous-integration/gitbook/mobi GitBook build "mobi" is pending Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 1 failing file. Details
✅ continuous-integration/gitbook/json GitBook build "json" succeeded Details
✅ continuous-integration/gitbook/website GitBook build "website" succeeded Details
✅ continuous-integration/gitbook/epub GitBook build "epub" succeeded Details

Commits

The new version differs by 21 commits .

b3b1098 -> v0.37.1
a804033 Merge pull request #450 from rollup/gh-447
490d428 skip symlink test on windows
70261d0 linting
2d7f8a7 merge master -> gh-447
3f39de8 Merge pull request #1143 from danez/recursive-functions
583b13d Improves tree-shaking by only considering program-level
b04e790 Merge pull request #1152 from kzc/1146
dfb8a3f Merge pull request #1144 from christopherthielen/master
b1e4384 Update comments describing property string generation
2521f2e be more leniant in processing ExportDefaultDeclaration (#1146)
bb546d3 Add test for bizzare moduleName
f43fd99 Access global.* using array notation
98abe24 Merge pull request #1151 from rollup/gh-957
2d32cdd implement gatherPossibleValues on ExternalDeclaration - fixes #957

There are 21 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 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

❌ bitHound - Code 1 failing file. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/nyc-10.2.0 at 100.0% 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 🌴

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 📦🚀

arlac77 / uti Goto Github PK

uti's Introduction

Hi there 👋

uti's People

Contributors

Stargazers

Watchers

uti's Issues

Version 0.41.6 of rollup just got published.

Version 0.45.1 of rollup just got published.

Version 0.41.4 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 4.3.3 of travis-deploy-once was just published.

4.3.3 (2018-01-23)

Bug Fixes

The devDependency semantic-release was updated from 15.13.16 to 15.13.17.

15.13.17 (2019-06-25)

Bug Fixes

Version 11.0.3 of nyc just got published.

Version 0.43.1 of rollup just got published.

Version 3.4.0 of mocha just got published.

🎉 Enhancements

🐛 Fixes

🔩 Other

Version 0.54.1 of rollup was just published.

Version 0.47.1 of rollup just got published.

Version 15.9.8 of semantic-release was just published.

15.9.8 (2018-08-10)

Bug Fixes

Version 0.39.1 of rollup just got published.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Version 0.41.3 of rollup just got published.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

The devDependency semantic-release was updated from 15.13.20 to 15.13.21.

15.13.21 (2019-08-12)

Bug Fixes

Version 0.46.3 of rollup just got published.

Version 0.47.5 of rollup just got published.

🚨 The automated release from the master branch failed. 🚨

No npm token specified.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Version 3.4.2 of mocha just got published.

3.4.2 / 2017-05-24

🐛 Fixes

🔩 Other

Version 0.56.4 of rollup was just published.

The devDependency esm was updated from 3.0.84 to 3.1.0.

Version 0.47.3 of rollup just got published.

Version 11.1.0 of nyc just got published.

Version 0.60.1 of rollup was just published.

Version 3.3.0 of mocha just got published.

🎉 Enhancements

🐛 Fixes

🔍 Coverage

🔩 Other

Version 10.3.0 of nyc just got published.

Version 10.1.0 of nyc just got published.

Version 0.40.1 of rollup just got published.

🚨 The automated release from the master branch failed. 🚨

No npm token specified.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Version 0.60.7 of rollup was just published.

Version 0.46.2 of rollup just got published.

🚨 The automated release from the master branch failed. 🚨

No npm token specified.

Version 0.45.2 of rollup just got published.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Version 0.41.5 of rollup just got published.

Version 10.3.2 of nyc just got published.

Version 0.39.2 of rollup just got published.

Version 0.37.1 of rollup just got published.

Version 10.2.0 of nyc just got published.

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

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

The devDependency semantic-release was updated from `15.13.16` to `15.13.17`.

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

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

The devDependency semantic-release was updated from `15.13.20` to `15.13.21`.

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

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

The devDependency esm was updated from `3.0.84` to `3.1.0`.

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