Skip to content

Commit

Permalink
chore(master): release 1.5.0 (#380)
Browse files Browse the repository at this point in the history
🤖 I have created a release *beep* *boop*
---


##
[1.5.0](v1.4.1...v1.5.0)
(2024-01-02)


### Features

* tolerate dirty json
([#431](#431))
([07db8f7](07db8f7))


### Bug Fixes

* try checkout before release-please-action
([906c54e](906c54e))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
  • Loading branch information
github-actions[bot] authored Jan 3, 2024
1 parent 07db8f7 commit 7180b5e
Show file tree
Hide file tree
Showing 3 changed files with 15 additions and 3 deletions.
12 changes: 12 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,16 @@
<a name="1.1.2"></a>
## [1.5.0](https://github.com/blacha/pretty-json-log/compare/v1.4.1...v1.5.0) (2024-01-02)


### Features

* tolerate dirty json ([#431](https://github.com/blacha/pretty-json-log/issues/431)) ([07db8f7](https://github.com/blacha/pretty-json-log/commit/07db8f7f6c3b19df46ba06bd371e136881a270df))


### Bug Fixes

* try checkout before release-please-action ([906c54e](https://github.com/blacha/pretty-json-log/commit/906c54e58029e0107e4b59d3ed369b92853cd96a))

## [1.4.1](https://github.com/blacha/pretty-json-log/compare/v1.4.0...v1.4.1) (2023-04-30)


Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "pretty-json-log",
"version": "1.4.1",
"version": "1.5.0",
"bin": {
"pjl": "pjl.js"
},
Expand Down

0 comments on commit 7180b5e

Please sign in to comment.