Update conventional-github-releaser to version 1.1.3 🚀 #259

Closed
greenkeeperio-bot wants to merge 1 commits from greenkeeper-conventional-github-releaser-1.1.3 into development
greenkeeperio-bot commented 2016-06-14 11:50:38 +00:00 (Migrated from github.com)

Hello lovely humans,

conventional-github-releaser just published its new version 1.1.3.

State Update 🚀
Dependency conventional-github-releaser
New version 1.1.3
Type devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of conventional-github-releaser.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project

You rock!

🌴


GitHub Release

Bug Fixes

  • cli: config option issue (#19) (a958ea9)
  • cli: fix unit test error (6a80929)
  • test: use github user from env validable (c787ea4)

The new version differs by 6 commits .

  • f738213 chore(release): 1.1.3
  • 927a6c4 docs(CHANGELOG): 1.1.3
  • c787ea4 fix(test): use github user from env validable
  • 6a80929 fix(cli): fix unit test error
  • a958ea9 fix(cli): config option issue (#19)
  • 4cde7cc docs(README): add conventional-gitlab-releaser to related section

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? greenkeeper upgrade

Hello lovely humans, [conventional-github-releaser](https://www.npmjs.com/package/conventional-github-releaser) just published its new version 1.1.3. <table> <tr> <th align=left> State </th> <td> Update :rocket: </td> </tr> <tr> <th align=left> Dependency </td> <td> conventional-github-releaser </td> </tr> <tr> <th align=left> New version </td> <td> 1.1.3 </td> </tr> <tr> <th align=left> Type </td> <td> devDependency </td> </tr> </table> This version is **not covered** by your **current version range**. Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though. I recommend you look into these changes and try to get onto the latest version of conventional-github-releaser. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update. Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and while I’m just a bot, there is a group of people who are happy to teach me new things. [Let them know](https://github.com/greenkeeperio/greenkeeper/issues/new). Good luck with your project :sparkles: You rock! :palm_tree: --- [GitHub Release](https://github.com/conventional-changelog/conventional-github-releaser/releases/tag/v1.1.3) <h3>Bug Fixes</h3> <ul> <li> <strong>cli:</strong> config option issue (<a href="https://urls.greenkeeper.io/conventional-changelog/conventional-github-releaser/pull/19" class="issue-link js-issue-link" data-url="https://github.com/conventional-changelog/conventional-github-releaser/issues/19" data-id="158678529" data-error-text="Failed to load issue title" data-permission-text="Issue title is private">#19</a>) (<a href="https://urls.greenkeeper.io/conventional-changelog/conventional-github-releaser/commit/a958ea9">a958ea9</a>)</li> <li> <strong>cli:</strong> fix unit test error (<a href="https://urls.greenkeeper.io/conventional-changelog/conventional-github-releaser/commit/6a80929">6a80929</a>)</li> <li> <strong>test:</strong> use github user from env validable (<a href="https://urls.greenkeeper.io/conventional-changelog/conventional-github-releaser/commit/c787ea4">c787ea4</a>)</li> </ul> --- The new version differs by 6 commits . - [`f738213`](https://github.com/conventional-changelog/conventional-github-releaser/commit/f7382131237a28846ce2c856ed1de2acc2a92054) <code>chore(release): 1.1.3</code> - [`927a6c4`](https://github.com/conventional-changelog/conventional-github-releaser/commit/927a6c40113de386972598f2774cac55918540d4) <code>docs(CHANGELOG): 1.1.3</code> - [`c787ea4`](https://github.com/conventional-changelog/conventional-github-releaser/commit/c787ea4bf051043122fdfe481b9d1ae70ec8f3fd) <code>fix(test): use github user from env validable</code> - [`6a80929`](https://github.com/conventional-changelog/conventional-github-releaser/commit/6a80929a764362c8cca4ef100c6e74e3808021c4) <code>fix(cli): fix unit test error</code> - [`a958ea9`](https://github.com/conventional-changelog/conventional-github-releaser/commit/a958ea92871a785678235046c3c9df9e017f0982) <code>fix(cli): config option issue (#19)</code> - [`4cde7cc`](https://github.com/conventional-changelog/conventional-github-releaser/commit/4cde7cc57b09b387374d5521700f7ff6d53d8b21) <code>docs(README): add conventional-gitlab-releaser to related section</code> See the [full diff](https://github.com/conventional-changelog/conventional-github-releaser/compare/c983d18e3eb6059e97a37d3897d150bfb55d049e...f7382131237a28846ce2c856ed1de2acc2a92054). --- This pull request was created by [greenkeeper.io](https://greenkeeper.io/). <sub>Tired of seeing this sponsor message? :zap: `greenkeeper upgrade`</sub>

Pull request closed

Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dc/ng2-file-upload#259