search

digitalsadhu / loopback-component-jsonapi

JSONAPI support for loopback.
MIT License
101 stars 32 forks source link

Update semantic-release to the latest version 🚀 #266

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 12.2.2 of semantic-release was just published.

Dependency semantic-release
Current Version 11.2.0
Type devDependency

The version 12.2.2 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of semantic-release.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Release Notes v12.2.2

12.2.2 (2018-01-13)

Bug Fixes

  • set node minimum version to 8.3 (cc0c312)
Commits

The new version differs by 21 commits.

  • cc0c312 fix: set node minimum version to 8.3
  • 93173e2 fix(package): update execa to version 0.9.0
  • 48ade92 chore(package): update prettier to version 1.10.0
  • 49ad198 docs(contrib): add atomic commits requirement
  • adbcca6 docs: add issue template
  • e0b4e6a docs: add CONTRIBUTING guidelines
  • 53f3de6 feat: allow to exclude commits from analysis
  • fd54eea docs: update Yarn FAQ
  • ba79c85 docs: typos. clarifications
  • 75778bc docs: troubleshooting
  • d6c398f docs: add heading anchor
  • fdb995f docs: publish with gitbook
  • ed89361 docs: documentation improvements
  • f4d9ebe fix(security): Updated marked dependency
  • 5bc46a0 feat: allow to release from local machine

There are 21 commits in total.

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper bot :palm_tree:

coveralls commented 6 years ago

Coverage Status

Coverage remained the same at 94.472% when pulling 3b392facf0bb3836120527d759ff8cb5fbef52b4 on greenkeeper/semantic-release-12.2.2 into cd6ab2da4a3dd4c88be422b861e18ad9b30b6f38 on master.

coveralls commented 6 years ago

Coverage Status

Coverage remained the same at 94.472% when pulling 3b392facf0bb3836120527d759ff8cb5fbef52b4 on greenkeeper/semantic-release-12.2.2 into cd6ab2da4a3dd4c88be422b861e18ad9b30b6f38 on master.

coveralls commented 6 years ago

Coverage Status

Coverage remained the same at 94.554% when pulling f4e0b3e3ee831ce3669301e1ed8f2c3b3a2c12bc on greenkeeper/semantic-release-12.2.2 into 9ce761b09a7c5ef9d8011a94a8c159ef9e690c44 on master.

coveralls commented 6 years ago

Coverage Status

Coverage remained the same at 94.554% when pulling f4e0b3e3ee831ce3669301e1ed8f2c3b3a2c12bc on greenkeeper/semantic-release-12.2.2 into 9ce761b09a7c5ef9d8011a94a8c159ef9e690c44 on master.

coveralls commented 6 years ago

Coverage Status

Coverage remained the same at 94.554% when pulling f4e0b3e3ee831ce3669301e1ed8f2c3b3a2c12bc on greenkeeper/semantic-release-12.2.2 into 9ce761b09a7c5ef9d8011a94a8c159ef9e690c44 on master.

Tronix117 commented 6 years ago

I added travis-deploy-once, and I separated in multiple after-success steps to have better tracability in logs. I also added commitlint, comitizen and conventional config for commitlint. I tested the commit stuff, but I couldn't really test semantic-release, I guess we will need to merge to know for sure.