0.6.1

This release contains a little breaking change when it comes to the calculation of updateCount. Previously, every record/delete action within a stub result in an increment of this counter. This could result in a single request increasing the counter by more than 1 (and it was also documented + tested that way)

With this change it is now guaranteed that a single request only increases the counter by 1 and therefore has a more consistent behavior.

Furthermore, the hasContext matcher now allows to use WireMock's built-in matchers on properties and list entries, thus providing extended flexibility.

💥 Breaking changes

• bug!: fix updateCount handling (#110) @dirkbolte

🚀 New features and improvements

• feat: support built-in WireMock matchers on properties and list entries (#109) @dirkbolte

🐛 Bug fixes

• bug!: fix updateCount handling (#110) @dirkbolte