pvdlg/cz-conventional-commit

Commitizen adapter following the conventional-changelog format, with emojis. 🎉

cz-conventional-commit's Issues

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

Version 1.6.0 of prettier just got published.

Branch	Build failing 🚨
Dependency	prettier
Current Version	1.5.3
Type	devDependency

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

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

1.6.0: Config File, JSX

I want to give a special shout out to @azz who has been maintaining the repository and implementing a bunch of the changes in this release as I had less time to devote to prettier due to vacation and switching team :)

Highlights

Configuration

Implement cosmiconfig for workspace configuration (#2434) by @azz

Since the very first release of prettier, people have asked for a .prettierrc file. We've been trying to have as few options as possible and tried to avoid being one more .dotfile that you have to have when starting a new project.

But, the truth is, we need to have some way to configure prettier that can be kept in sync with all the integrations. By not having one, we pushed the problem to them and saw a bunch of incompatible ways of handling the problem. So now, it's handled by prettier itself.

// .prettierrc
{
  "trailingComma": "es5",
  "singleQuote": true
}

For more information on configuration file support, see the README.

Support .prettierignore files (#2412) by @evilebottnawi

Along with telling what configuration to use, you can write a file .prettierignore to tell which files not to convert.

# .prettierignore
dist/
package.json

JSX

Improve JSX Formatting (#2398) by @suchipi

The last big friction point from people trying to adopt prettier was around how JSX was being printed. We went through all the issues that were raised and made a bunch of changes:

• Arrow Function Expressions returning JSX will now add parens when the JSX breaks

// Before
const Component = props =>
  <div>
    Hello {props.name}!
  </div>;
// After

const Component = props => (

<div>

Hello {props.name}!

</div>

);

• Conditional expressions within (or containing) JSX are formatted in a different way using parenthesis

// Before
<div>
  {props.isVisible
    ? <BaseForm
        url="/auth/google"
        method="GET"
      />
    : <Placeholder />}
</div>;
// After

<div>

{props.isVisible ? (

<BaseForm

url="/auth/google"

method="GET"

/>

) : (

<Placeholder />

)}

</div>

• JSX in logical expressions (|| or &&) is always wrapped in parens when the JSX breaks

// Before
<div>
  {props.isVisible &&
    <BaseForm
      url="/auth/google"
      method="GET"
    />}
</div>;
// After

<div>

{props.isVisible && (

<BaseForm

url="/auth/google"

method="GET"

/>

)}

</div>

Hopefully this is going to be more in line with how the majority of the community is writing JSX and we can have prettier be used in more place ;)

Inline single expressions in JSX (#2442) by @karl

With JSX, we started by respecting a lot of line breaks that were in the original source. This had the advantage of doing fewer changes to your codebase but chipped away the value of a consistent pretty printer as the same semantic code could be written in two ways.

During each new release we've tightened this and made decisions around how to always print a piece of code. The latest of those is what happens if there's a single child in a JSX object, we're now always going to inline it.

// Before
return (
  <div>
    {this.props.test}
  </div>
);
return <div>{this.props.test}</div>;
// After

return <div>{this.props.test}</div>;

return <div>{this.props.test}</div>;

Ensure there is a line break after leading JSX white space (#2348) by @karl

Leading JSX empty spaces are now on their own line. It looked weird to have them before a tag as it "indented" it differently compared to the rest.

// Before
<span className="d1">
  {' '}<a
    href="https://github.schibsted.io/finn/troika"
    className="link"
  />
</span>
// After

<span className="d1">

{' '}

<a

href="https://github.schibsted.io/finn/troika"

className="link"

/>

</span>

Other Changes

JSON

Use babylon.parseExpression for JSON (#2476) by @josephfrazier

We used to use a strict JSON parser that would throw if there was a comment or a trailing comma. This was inconvenient as many JSON files in practice are parsed using JavaScript or json5 that are not as strict. Now, we have relaxed this and are using the JavaScript parser to parse and print JSON. This means that comments will be maintained if there were some.

Note that this is purely additive, if your original file was JSON compliant, it will keep printing a valid JSON.

// Before
Syntax error
// After

{ / some comment / "a": 1 }

JavaScript

Add more supervisory parens (#2423) by @azz

Parenthesis are a hot topic because they are not part of the AST, so prettier ignores all the ones you are putting and re-creating them from scratch. We went through all the things that people reported and came up with a few edge cases that were very confusing when comparisons were chained and % was mixed with * or /.

One thing that we are not changing is the fact that we remove extra parenthesis around combinations of basic arithmetic operators: +-*/.

// Before
x !== y === z;
x * y % z;
// After

(x !== y) === z;

(x * y) % z;

Implement prettier-ignore inside JSX (#2487) by @azz

It's useful to be able to ignore pieces of JSX, it's now possible to add a comment inside of a JSX expression to ignore the formatting of the next element.

// Before
<Component>
  {/*prettier-ignore*/}
  <span ugly format="" />
</Component>
// Before

<Component>

{/prettier-ignore/}

<span     ugly  format=''   />

</Component>

Do not swallow prettier-ignore comments (#2664)

In order to support some edge cases, in the internals, we have the ability to avoid printing comments in a generic way and print them in the call site instead. It turns out that when we used prettier-ignore, we didn't print the comments at all! This is now fixed.

// Before
push(
  <td> :)
  </td>,
);
// After

push(

// prettier-ignore

<td> :)

</td>,

);

Fix indentation of a do-while condition (#2359) by @jsnajdr

It took 6 months for someone to report that do-while were broken when the while condition is multi-line, it confirms my hunch that this construct is not widely used in practice.

// Before
do {} while (
  someVeryLongFunc(
  someVeryLongArgA,
  someVeryLongArgB,
  someVeryLongArgC
)
);
// After

do {} while (

someVeryLongFunc(

someVeryLongArgA,

someVeryLongArgB,

someVeryLongArgC

)

);

Break sequence expressions (#2388) by @bakkot

Another underused feature of JavaScript is sequence expressions. We used to do a bad job at printing them when they would go multi-line, this has been corrected :)

// Before
(a = b ? c : "lllllllllllllllllllllll"), (a = b
  ? c
  : "lllllllllllllllllllllll"), (a = b ? c : "lllllllllllllllllllllll"), (a = b
  ? c
  : "lllllllllllllllllllllll"), (a = b ? c : "lllllllllllllllllllllll");
// After

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll')

Trim trailing whitespace from comments (#2494) by @azz

We took the stance with prettier to remove all the trailing whitespaces. We used to not touch comments because it's user generated, but that doesn't mean that they should have whitespace :)

// Before
// There is some space here ->______________
// After

// There is some space here ->

Fix interleaved comments in class decorators (#2660, #2661)

Our handling for comments inside of the class declaration was very naive, we would just move all the comments to the top. We now are more precise and respect the comments that are interleaved inside of decorators and around extends.

// Before
// A
// B
// C
@Foo()
@Bar()
class Bar {}
// After

// A

@Foo()

// B

@Bar()

// C

class Bar {}

Improve bind expression formatting (#2493) by @azz

Bind expressions are being discussed at TC39 and we figured we could print it with prettier. We used to be very naive about it and just chain it. Now, we use the same logic as we have for method chaining with the . operator for it. We also fixed some edge cases where it would output invalid code.

// Before
observable::filter(data => data.someTest)::throttle(() =>
  interval(10)::take(1)::takeUntil(observable::filter(data => someOtherTest))
)::map(someFunction);
// After

observable

::filter(data => data.someTest)

::throttle(() =>

interval(10)::take(1)::takeUntil(observable::filter(data => someOtherTest))

)

::map(someFunction);

Add support for printing optional catch binding (#2570) by @existentialism

It's being discussed at TC39 to be able to make the argument of a catch(e) optional. Let's make sure we can support it in prettier if people use it.

// Before
Syntax error
// After

try {} catch {}

Add support for printing optional chaining syntax (#2572) by @azz

Another new proposal being discussed at TC39 is an optional chaining syntax. This is currently a stage 1 proposal, so the syntax may change at any time.

obj?.prop       // optional static property access
obj?.[expr]     // optional dynamic property access
func?.(...args) // optional function or method call

Handle Closure Compiler type cast syntax correctly (#2484) by @yangsu

Comments are tricky to get right, but especially when they have meaning based on where they are positioned. We're now special casing the way we deal with comments used as type cast for Closure Compiler such that they keep having the same semantics.

// Before
let assignment /** @type {string} */ = getValue();
// After

let assignment = /** @type {string} */ (getValue());

Inline first computed property lookup in member chain (#2670) by @azz

It looks kind of odd to have a computed property lookup on the next line, so we added a special case to inline it.

// Before
data
  [key]('foo')
  .then(() => console.log('bar'))
  .catch(() => console.log('baz'));
// After

data[key]('foo')

.then(() => console.log('bar'))

.catch(() => console.log('baz'));

Flow

Support opaque types and export star (#2543, #2542) by @existentialism

The flow team introduced two very exciting features under a new syntax. We now support them in prettier. I've personally been waiting for opaque types for a veerrryyyy long time!

// Before
Syntax error
// After

opaque type ID = string;

export type * from "module";

Strip away unnecessary quotes in keys in type objects and interfaces (#2643)

We've been doing this on JavaScript objects since the early days of prettier but forgot to apply the same thing to Flow and TypeScript types.

// Before
type A = {
  "string": "A";
}
// After

type A = {

string: "A";

}

Print TypeParameter even when unary function type (#2406) by @danwang

Oopsy, we were dropping the generic in this very specific case.

// Before
type myFunction = A => B;
// After

type myFunction = <T>(A) => B;

Keep parens around FunctionTypeAnnotation inside ArrayTypeAnnotation (#2561) by @azz

Parenthesis... someday we'll get all of them fixed :)

// Before
const actionArray: () => void[] = [];
// After

const actionArray: (() => void)[] = [];

TypeScript

Support TypeScript 2.5 RC (#2672) by @azz

TypeScript 2.5 RC was recently announced, allowing you to use the upcoming "optional catch binding" syntax in TypeScript, too. 🎉

Don't add namespace keyword to global declaration (#2329) by @azz

// Before
namespace global {
  export namespace JSX {  }
}
// After

global {

export namespace JSX {}

}

Fix <this.Component /> (#2472) by @backus

Thanks to the untyped and permissive nature of JavaScript, we've been able to concat undefined to a string and get some interesting code as a result. Now fixed for this case :)

// Before
<undefined.Author />
// After

<this.Author />

Allow type assertions to hug (#2439) by @azz

We want to make sure that all the special cases that we added for JavaScript and Flow also work for TypeScript constructs. In this case, objects should also hug if they are wrapped in a as operator.

// Before
const state = JSON.stringify(
  {
    next: window.location.href,
    nonce,
  } as State
);
// After

const state = JSON.stringify({

next: window.location.href,

nonce,

} as State);

Remove parens for type assertions in binary expressions (#2419) by @azz

Most of the time we add parenthesis for correctness but in this case, we added them for nothing, so we can just get rid of them and have a cleaner code :)

// Before
(<x>a) || {};
// After

<x>a || {};

Print parens around type assertion as LHS in assignment (#2525) by @azz

Yet another case of missing parenthesis. Thankfully we're getting very few of them nowadays and they are for extremely rare edge cases.

// Before
foo.bar as Baz = [bar];
// After

(foo.bar as Baz) = [bar];

Print declare for TSInterfaceDeclaration (#2574) by @existentialism

The declare keyword doesn't do anything for interface so we never put it there. However, it felt weird if you were in a declaration file and seeing everything have declare before it except for interfaces. So now we reprint declare if it was there in the first place.

// Before
interface Dictionary<T> {
  [index: string]: T
}
// After

declare interface Dictionary<T> {

[index: string]: T

}

CSS

Normalize quotes in CSS (#2624) by @lydell

In order to get a first version of CSS to ship, we kept string quotes as is. We are now respecting the singleQuote option of prettier. The difficulty here was to make sure that we output correct code for all the crazy escapes, unicode characters, emoji, special rules like charset which only work with double quotes...

// Before
div {
  content: "abc";
}
// After

div {

content: 'abc';

}

Normalize numbers in CSS (#2627) by @lydell

Another place where we can reuse the logic we've done for JavaScript to improve CSS printing.

// Before
border: 1px solid rgba(0., 0.0, .0, .3);
// After

border: 1px solid rgba(0, 0, 0, 0.3);

Quote unquoted CSS attribute values in selectors (#2644) by @lydell

I can never quite remember the rules behind quotes around attributes so we're now always putting quotes there.

// Before
a[id=test] {}
// After

a[id="test"] {}

Add support for css keyword (#2337) by @zanza00

// Before
const header = css`.top-bar {background: black;margin: 0;position: fixed;}`
// After

const header = css</span></span> <span class="pl-s">  .top-bar {</span> <span class="pl-s">    background: black;</span> <span class="pl-s">    margin: 0;</span> <span class="pl-s">    position: fixed;</span> <span class="pl-s">  }</span> <span class="pl-s"><span class="pl-pds">;

Support styled-components with existing component (#2552, #2619) by @azz

styled-components has a lot of different variants for tagging template literals as CSS. It's not ideal that we've got to encode all those ways inside of prettier but since we started, might as well do it for real.

styled(ExistingComponent)`
  css: property;
`;
styled.button.attr({})</span></span> <span class="pl-s">  border: rebeccapurple;</span> <span class="pl-s"><span class="pl-pds">;

Trim whitespace in descendant combinator (#2411) by @azz

The CSS parsers we use do not give us a 100% semantic tree: in many occasions they bail and just give us what is being entered. It's up to us to make sure we clean this up while maintaining correctness. In this case, we just printed spaces between selectors as is but we know it's correct to always replace it by a single space.

// Before
.hello
        .<span class="pl-smi">how</span><span class="pl-k">-</span>you<span class="pl-k">-</span>doin {

height: 42;

}
// After

.hello .how-you-doin {

height: 42;

}

Strip BOM before parsing (#2373) by @azz
I still have nightmares from dealing with BOM in a previous life. Thankfully, in 2017 it's no longer a big issue as most tooling is now aware of it. Thanks @azz for fixing an edge cases related to CSS parsing.
// Before
[BOM]/* Block comment *
html {
  content: "#{1}";  
}
// After
[BOM]/* Block comment */
html {
  content: "#{1}";  
}
GraphQL
Add support for range-formatting GraphQL (#2319) by @josephfrazier
If you tried to use the range formatting feature in a GraphQL file, it would throw an exception, now it properly worked again and only reformats the piece you selected.
Add .gql file extension to be parsed as GraphQL (#2357) by @rrdelaney
At Facebook, we use .graphql extension but it looks like it's common to have .gql as well, doesn't cost a lot to support it in the heuristic that figures out what parser to use.
CLI
Support multiple patterns with ignore pattern (#2356) by @evilebottnawi
It was already possible to have multiple glob patterns but they would be additive, with this change, you can add a glob pattern to ignore some files. It should be very handy to ignore folders that are deeply nested.
prettier --write '{**/*,*}.{js,jsx,json}' '!vendor/**'
Make --list-different to work with --stdin (#2393) by @josephfrazier
This is a handy way of knowing if prettier would print a piece of code in a different way. We already had all the concepts in place, we just needed to wire them up correctly.
$ echo 'call ( ) ;' | prettier --list-different
(stdin)
$ echo $?
1

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

Version 1.7.1 of prettier just got published.

Branch	Build failing 🚨
Dependency	prettier
Current Version	1.7.0
Type	devDependency

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

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

---

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

Version 5.1.1 of sinon was just published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	5.1.0
Type	devDependency

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

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

• 4d12f95 Update docs/changelog.md and set new release id in docs/_config.yml
• 3ddfea0 Add release documentation for v5.1.1
• 67b8872 5.1.1
• 8ff4ac8 Update History.md and AUTHORS for new release
• 8aa1425 Remove ES2015 'module' field for 5x branch

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 🚨

Version 15.6.0 of semantic-release was just published.

Branch	Build failing 🚨
Dependency	[semantic-release](https://github.com/semantic-release/semantic-release)
Current Version	15.5.5
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.6.0

15.6.0 (2018-06-19)

Features

• allow to disable the publish plugin hook (4454d57)

Commits

The new version differs by 1 commits.

• 4454d57 feat: allow to disable the publish plugin hook

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

The dependency commitizen was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

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

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

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v3.1.2

3.1.2 (2019-07-17)

Bug Fixes

• deps: update dependency lodash to v4.17.14 [security] (#641) (1875a38), closes commitizen/cz-cli#639
• release fixed sem-release (#648) (4417fcf)
• update dependencies for security (#645) (b3dd4c4)

Commits

The new version differs by 5 commits.

• 4417fcf fix: release fixed sem-release (#648)
• b3dd4c4 fix: update dependencies for security (#645)
• 1875a38 fix(deps): update dependency lodash to v4.17.14 [security] (#641)
• 372c75e docs: highlight pre-requisties and bubble up related sections (#613)
• b24eade chore(security): fixed 5 vulnerabilities (#599)

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

Version 4.1.6 of sinon was just published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	4.1.5
Type	devDependency

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

sinon 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 10 commits.

• 68c37ed Update docs/changelog.md and set new release id in docs/_config.yml
• cd8ae51 Add release documentation for v4.1.6
• 29e80be 4.1.6
• a5c59a5 Update History.md and AUTHORS for new release
• 0ae60b6 Merge pull request #1653 from mroderick/upgrade-dependencies
• dcd4191 Upgrade browserify to latest
• a316f02 Upgrade markdownlint-cli to latest
• 78ebdb3 Upgrade lint-staged to latest
• fcf967b Upgrade dependency supports-color
• 7c3cb4f Enable StaleBot with default configuration (#1649)

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 🌴

Cannot find module 'conventional-changelog-metahub/types'

Getting the following error message when trying to commit:

Cannot find module 'conventional-changelog-metahub/types'
Require stack:
- /Users/timmclaren/Development/habits-app/node_modules/@metahub/cz-conventional-commit/index.js
- /Users/timmclaren/Development/habits-app/node_modules/commitizen/dist/commitizen/adapter.js
- /Users/timmclaren/Development/habits-app/node_modules/commitizen/dist/commitizen.js
- /Users/timmclaren/Development/habits-app/node_modules/commitizen/dist/cli/git-cz.js
- /Users/timmclaren/Development/habits-app/node_modules/commitizen/bin/git-cz.js
- /Users/timmclaren/Development/habits-app/node_modules/commitizen/bin/git-cz

Looks like conventional-changelog-metahub should be a dependency not a dev-dependency

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

The devDependency sinon was updated from 7.3.2 to 7.4.0.

🚨 View failing branch.

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

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

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

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

15.13.16 (2019-06-07)

Bug Fixes

• package: update env-ci to version 4.0.0 (8051294)

Commits

The new version differs by 3 commits.

• 4ed6213 style: fix prettier style
• 8051294 fix(package): update env-ci to version 4.0.0
• 95a0456 chore(package): update ava 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 lodash is breaking the build 🚨

The dependency lodash was updated from 4.17.11 to 4.17.12.

🚨 View failing branch.

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

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

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.10.8 to 15.11.0.

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

15.11.0 (2018-11-12)

Bug Fixes

• remove redundant log (728ea34)

Features

• support multiple plugins for the analyzeCommits step (5180001)

Commits

The new version differs by 6 commits.

• 5180001 feat: support multiple plugins for the analyzeCommits step
• 728ea34 fix: remove redundant log
• 83af7ac docs: mention default analyzeCommits plugin
• 8e564eb docs: update FAQ to reflect new plugins option
• dff1f10 docs: mention postversion npm script hook to run build scripts
• ae4995c style: fix prettier errors

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

Version 5.0.9 of sinon was just published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	5.0.8
Type	devDependency

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

sinon 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 5 commits.

• 86b930c Update docs/changelog.md and set new release id in docs/_config.yml
• 033aa60 Add release documentation for v5.0.9
• 3321085 5.0.9
• 9f321d5 Update History.md and AUTHORS for new release
• e862196 Upgrade @std/esm to esm.

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

Version 6.0.1 of sinon was just published.

Branch	Build failing 🚨
Dependency	[sinon](https://github.com/sinonjs/sinon)
Current Version	6.0.0
Type	devDependency

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

sinon 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 8 commits.

• c8901e7 Update docs/changelog.md and set new release id in docs/_config.yml
• 8f8b2d9 Add release documentation for v6.0.1
• feee43d 6.0.1
• fc21226 Update History.md and AUTHORS for new release
• a3cf98f Add fake behaviors to sandbox (#1815)
• 8816e1a Use escaped double quotes for compatibility with Windows
• 559d57d Fix mocha test file pattern to match subdirectories correctly
• d2983f1 Use migration guide include in guide index (#1838)

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

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

Version 4.4.7 of sinon was just published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	4.4.6
Type	devDependency

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

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

• e060fe9 Update docs/changelog.md and set new release id in docs/_config.yml
• e9fce06 Add release documentation for v4.4.7
• f047838 4.4.7
• cc91fe6 Update History.md and AUTHORS for new release
• 9fb8577 Emojify the support message :heart:
• a87ef85 Use existing mini-lib for coloring
• 1f33fe5 Reduce noisy NPM output from postinstall script

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

The devDependency conventional-commits-parser was updated from 3.0.3 to 3.0.5.

🚨 View failing branch.

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

conventional-commits-parser 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 25 commits.

• 7c1c8ad Publish
• c493556 chore(deps): lock file maintenance
• bfeed12 Publish
• 4ec6f41 chore(conventional-changelog-writer): bump handlebars to 4.4.0 (#528)
• 2de0195 chore(deps): lock file maintenance
• faa2819 docs(readme): fix typo (#524)
• 7a60dec fix: use full commit hash in commit link
• b63a5ff fix(preset, eslint): display short tag in release notes
• c0566ce fix(preset, conventionalcommits): fix handling conventionalcommits preset without config object
• 417139c revert: "fix(preset-loader): fix handling conventionalcommits preset without config object" (#520)
• a3acc32 feat: sort sections of CHANGELOG based on priority (#513)
• 6425972 fix(preset-loader): fix handling conventionalcommits preset without config object
• 958d243 fix(preset, conventionalcommits): pass issuePrefixes to parser (#510)
• 1ed96fd docs: Update README.md (#508)
• c0bac28 fix(deps): update dependency tempfile to v3 (#459)

There are 25 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 eslint-config-pretty is breaking the build 🚨

Version 2.1.0 of eslint-config-pretty just got published.

Branch	Build failing 🚨
Dependency	eslint-config-pretty
Current Version	2.0.2
Type	devDependency

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

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

v2.1.0

2.1.0 (2017-09-02)

✨ Features

• base: Add function-paren-newline rule (a105db7), closes #25

🚨 Tests

• Use nyc configuration from package.json (cd8e074)

⚙️ Continuous Integrations

• travis: Retry npm install if it fails (28da4ad)

♻️ Chores

• package: update eslint to version 4.6.0 (7131c2f)

Commits

The new version differs by 4 commits.

• a105db7 feat(base): Add function-paren-newline rule
• 7131c2f chore(package): update eslint to version 4.6.0
• 28da4ad ci(travis): Retry npm install if it fails
• cd8e074 test: Use nyc configuration from package.json

See the full diff

Not sure how things should work exactly?

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

---

Your Greenkeeper Bot 🌴

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

The devDependency codecov was updated from 3.5.0 to 3.6.0.

🚨 View failing branch.

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

codecov 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 11 commits.

• 2ed978c v3.6.0
• 024cced Merge pull request #135 from iansu/codebuild
• 24a0a76 Merge branch 'master' into codebuild
• f628c33 Merge pull request #145 from fabiendem/semaphore-compat
• 0c57093 Rename semaphore v2 clearly in tests
• 5a5c489 Add retro-compatibility for Semaphore 1.x and maintain support for 2.x
• a45a9b5 Revert "Updates Semaphore CI Service for 2.0 (#132)"
• e2f6b81 Test improvements
• 3faacd4 Add support for AWS CodeBuild
• 8371836 Create CODE_OF_CONDUCT.md (#133)
• 6167aa8 Updates Semaphore CI Service for 2.0 (#132)

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 🚨

Version 15.7.0 of semantic-release was just published.

Branch	Build failing 🚨
Dependency	semantic-release
Current Version	15.6.6
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.7.0

15.7.0 (2018-07-10)

Bug Fixes

• do not set path to plugin config defined as a Function or an Array (f93eeb7)

Features

• allow to define multiple generateNotes plugins (5989989)

Commits

The new version differs by 12 commits.

• 24ce560 refactor: build plugin pipeline parameters at initialization
• eb26254 refactor: use Object.entries rather than Object.keys
• 50061bb refactor: remove unnecessary object destructuring
• 5989989 feat: allow to define multiple generateNotes plugins
• 576eb60 refactor: simplify plugin validation
• f7f4aab refactor: use the lastInput arg to compute the prepare pipeline next input
• 12de628 refactor: fix incorrect comments in lib/plugins/pipeline.js
• d303286 docs: fix default value for analyzeCommits plugin
• ed9c456 refactor: always return an Array of results/errors from a plugin pipeline
• cac4882 docs: clarify verifyRelease plugin description
• 09348f1 style: disable max-params warning for lib/plugins/normalize.js
• f93eeb7 fix: do not set path to plugin config defined as a Function or an Array

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

The dependency conventional-changelog-metahub was updated from 2.0.2 to 2.0.3.

🚨 View failing branch.

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

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

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v2.0.3

2.0.3 (2019-10-14)

🐛 Bug Fixes

• set shortHash to commit object (7c3b24c)

♻️ Chores

• package: update ava to version 1.0.1 (0ce98c7)
• package: update conventional-changelog to version 3.0.1 (06ca95d)
• package: update emoji-regex to version 7.0.0 (4e1d63d)
• package: update emoji-regex to version 8.0.0 (37b7ae8)
• package: update execa to version 0.11.0 (bc6f4d2)
• package: update execa to version 1.0.0 (a05cb6a)
• package: update fs-extra to version 7.0.0 (656a460)
• package: update get-stream to version 4.0.0 (a2bd6b2)
• package: update nyc (413bc4d)
• package: update nyc to version 14.0.0 (57ff2a4)
• package: update xo to version 0.22.0 (9b25fed)
• package: update xo to version 0.23.0 (87dd6e0)
• package: update xo to version 0.24.0 (20fdb01)

Commits

The new version differs by 14 commits.

• 7c3b24c fix: set shortHash to commit object
• 20fdb01 chore(package): update xo to version 0.24.0
• 57ff2a4 chore(package): update nyc to version 14.0.0
• 37b7ae8 chore(package): update emoji-regex to version 8.0.0
• 0ce98c7 chore(package): update ava to version 1.0.1
• 413bc4d chore(package): update nyc
• 06ca95d chore(package): update conventional-changelog to version 3.0.1
• 87dd6e0 chore(package): update xo to version 0.23.0
• a05cb6a chore(package): update execa to version 1.0.0
• bc6f4d2 chore(package): update execa to version 0.11.0
• a2bd6b2 chore(package): update get-stream to version 4.0.0
• 9b25fed chore(package): update xo to version 0.22.0
• 656a460 chore(package): update fs-extra to version 7.0.0
• 4e1d63d chore(package): update emoji-regex to version 7.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.32 to 15.14.0.

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

15.14.0 (2019-12-21)

Features

• pass envi-ci values to plugins context (a8c747d)

Commits

The new version differs by 2 commits.

• a8c747d feat: pass envi-ci values to plugins context
• fc70726 chore: add Mockserver generated file to gitignore

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 🌴

Can't enable emojis

Emojis cannot be enabled from the configuration file, the default configuration always takes precedence when the package is initialised.

cz-conventional-commit/index.js

Lines 8 to 10 in e0c01ca

	const config = _.merge(commitizen.configLoader.load(), {
	'cz-conventional-commit': {maxSubjectLength: 72, bodyLineLength: 100, emoji: false},
	})['cz-conventional-commit'];