Skip to content

Commit

Permalink
chore: release 4.0.0 (#383)
Browse files Browse the repository at this point in the history
🤖 I have created a release \*beep\* \*boop\* 
---
## [4.0.0](https://github.com/googleapis/release-please/compare/v3.3.0...v4.0.0) (2020-03-27)


### ⚠ BREAKING CHANGES

* upgrade octokit/gts/typescript (#381)

### Code Refactoring

* upgrade octokit/gts/typescript ([#381](https://github.com/googleapis/release-please/issues/381)) ([4e0bf11](https://github.com/googleapis/release-please/commit/4e0bf11b7f4217b5c6b8cd1aa9ea4db1bce06b89))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please).
  • Loading branch information
release-please[bot] authored Mar 27, 2020
1 parent 4e0bf11 commit d1cffce
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 1 deletion.
11 changes: 11 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,17 @@

[1]: https://www.npmjs.com/package/release-please?activeTab=versions

## [4.0.0](https://github.com/googleapis/release-please/compare/v3.3.0...v4.0.0) (2020-03-27)


### ⚠ BREAKING CHANGES

* upgrade octokit/gts/typescript (#381)

### Code Refactoring

* upgrade octokit/gts/typescript ([#381](https://github.com/googleapis/release-please/issues/381)) ([4e0bf11](https://github.com/googleapis/release-please/commit/4e0bf11b7f4217b5c6b8cd1aa9ea4db1bce06b89))

## [3.3.0](https://github.com/googleapis/release-please/compare/v3.2.3...v3.3.0) (2020-03-20)


Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "release-please",
"version": "3.3.0",
"version": "4.0.0",
"description": "generate release PRs based on the conventionalcommits.org spec",
"main": "./build/src/index.js",
"bin": "./build/src/bin/release-please.js",
Expand Down

0 comments on commit d1cffce

Please sign in to comment.