Version 1.2.0 of generate-changelog just got published.

Branch	Build failing 🚨
Dependency	generate-changelog
Current Version	1.1.0
Type	devDependency

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

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

• 807e2e4 1.2.0
• 6de2399 updated CHANGELOG.md
• 7bdbe7a Merge pull request #16 from tvardy/allow-no-category
• 11fbbd9 Merge pull request #15 from tvardy/exclude
• a859a9b fix(writer): don't print category if empty
• 006a2a0 test(package): fix coverage for lib/package.js
• fc31e9a feat(exclude): add -x, --exclude option

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 🌴

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency eslint-plugin-standard to v5
• chore(deps): update dependency husky to v9
• chore(deps): update dependency mocha to v10
• chore(deps): update dependency node to v20
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update dependency eslint-plugin-node to v11

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency chai to v4.4.1
• chore(deps): update dependency eslint-plugin-import to v2.29.1
• chore(deps): update dependency chai to v5
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency eslint-config-standard to v17
• chore(deps): update dependency eslint-plugin-promise to v6
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency nock to v13
• chore(deps): update dependency prettier-standard to v16
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

npm

package.json

• chai 4.3.4
• eslint 5.16.0
• eslint-config-standard 11.0.0
• eslint-plugin-import 2.23.0
• eslint-plugin-node 7.0.1
• eslint-plugin-promise 3.8.0
• eslint-plugin-standard 4.1.0
• generate-changelog 1.8.0
• husky 0.14.3
• istanbul 0.4.5
• lint-staged 7.3.0
• mocha 5.2.0
• nock 10.0.6
• prettier-standard 8.0.1
• node >=6

nvm

.nvmrc

• node v8

travis

.travis.yml

• node 6
• node 8

---

• Check this box to trigger a request for Renovate to run again on this repository

Version 4.0.1 of chai just got published.

Branch	Build failing 🚨
Dependency	chai
Current Version	4.0.0
Type	devDependency

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

As chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

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

---

Release Notes

4.0.1 / 2017-05-31

4.0.1

Of course, any major release cannot go without a quick bugfix release shortly after - and here's ours!

Bug Fixes

• Remove package.json browser field which was mistakenly added, and caused bundler tools like Browserify or Webpack to fail as it attempted to rebundle an already bundled file. (#978, #982)

Commits

The new version differs by 2 commits.

• b38b8d7 fix: (#978) remove browser field (#982)
• d0ace69 Update supported node version badge in README FIX #975

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 🌴

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: package.json
Error type: The renovate configuration file contains some invalid settings
Message: Configuration option 'packageRules[0].node' should be a json object, Invalid configuration option: author, Invalid configuration option: bugs, Invalid configuration option: eslintConfig, Invalid configuration option: eslintIgnore, Invalid configuration option: homepage, Invalid configuration option: keywords, Invalid configuration option: license, Invalid configuration option: lint-staged, Invalid configuration option: main, Invalid configuration option: name, Invalid configuration option: packageRules[2].chai, Invalid configuration option: packageRules[2].eslint, Invalid configuration option: packageRules[2].eslint-config-standard, Invalid configuration option: packageRules[2].eslint-plugin-import, Invalid configuration option: packageRules[2].eslint-plugin-node, Invalid configuration option: packageRules[2].eslint-plugin-promise, Invalid configuration option: packageRules[2].eslint-plugin-standard, Invalid configuration option: packageRules[2].generate-changelog, Invalid configuration option: packageRules[2].husky, Invalid configuration option: packageRules[2].istanbul, Invalid configuration option: packageRules[2].lint-staged, Invalid configuration option: packageRules[2].mocha, Invalid configuration option: packageRules[2].nock, Invalid configuration option: packageRules[2].prettier-standard, Invalid configuration option: renovate, Invalid configuration option: scripts, Invalid configuration option: tonicExampleFilename, Invalid configuration option: version, The "node" object can only be configured at the top level of a config but was found inside "packageRules[0]"

Version 4.0.2 of chai just got published.

Branch	Build failing 🚨
Dependency	chai
Current Version	4.0.1
Type	devDependency

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

As chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

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

---

Release Notes

4.0.2 / 2017-06-05

We have another bugfix release, addressing some issues for WebPack 1 users.

Bug Fixes

• Revert getting version information from package.json, some bundler tools like Webpack do not come default with json loaders despite Node being able to handle this. This change moves back to hardcoding the version number in the codebase. (#985, #986)

Commits

The new version differs by 1 commits.

• 616cf8b Revert get version package json (#986)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 9.0.9 of nock just got published.

Branch	Build failing 🚨
Dependency	nock
Current Version	9.0.8
Type	devDependency

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

As nock is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 4 commits .

• 5b1a8d8 9.0.9: Revert PR #802
• 51809e1 Merge pull request #840 from node-nock/revert-802-fix-754
• 0a083f6 Revert "Fix request timeout no working"
• 3728a1f Changelog v9.0.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 🌴