Skip to content

Commit

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


##
[0.7.23](v0.7.22...v0.7.23)
(2024-06-24)


### Build System or External Dependencies

* **deps:** Bump github.com/onsi/ginkgo/v2 from 2.17.1 to 2.19.0
([#167](#167))
([b0bef4d](b0bef4d))
* **deps:** Bump github.com/onsi/gomega from 1.33.0 to 1.33.1
([#156](#156))
([6bd9fd4](6bd9fd4))

---
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 Jun 24, 2024
1 parent 8b3e9f6 commit fb07844
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 1 deletion.
2 changes: 1 addition & 1 deletion .release-please-manifest.json
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
".": "0.7.22"
".": "0.7.23"
}
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# Changelog

## [0.7.23](https://github.com/runfinch/common-tests/compare/v0.7.22...v0.7.23) (2024-06-24)


### Build System or External Dependencies

* **deps:** Bump github.com/onsi/ginkgo/v2 from 2.17.1 to 2.19.0 ([#167](https://github.com/runfinch/common-tests/issues/167)) ([b0bef4d](https://github.com/runfinch/common-tests/commit/b0bef4dce3f62e58c70eff28b9178cd4f6a2d6e3))
* **deps:** Bump github.com/onsi/gomega from 1.33.0 to 1.33.1 ([#156](https://github.com/runfinch/common-tests/issues/156)) ([6bd9fd4](https://github.com/runfinch/common-tests/commit/6bd9fd45c423f56a782e62c9590ad2d85d6a2373))

## [0.7.22](https://github.com/runfinch/common-tests/compare/v0.7.21...v0.7.22) (2024-04-19)


Expand Down

0 comments on commit fb07844

Please sign in to comment.