1.6.0
A Quick Word from Us
Hello there! We just wanted to drop in and address the elephant in the room. In a previous release we made a promise to maintain API compatibility for future v1 releases. This release contains a few changes that may require minor updates to the way your code interacts with API request and response objects. These changes are necessary in order to make these APIs work properly for as many of you as possible.
One of our goals with this client library is to provide a working client that properly interacts with the PagerDuty Public API. While we remain committed to not breaking API compatibility for reasons such as "making the library [better | easier to use | etc.]"; we believe it is in all of our best interest to make this client library work.
As always, we welcome your feedback on this decision via a GitHub issue.
Highlights
- Returns custom error type
EventsAPIV2Error
for errors that occur with Events API (V2) calls by @theckman in #419 - List notifications API now works when using
includes
by @jaimegago in #439 - Improves support for macOS builds by @mjlshen in #434
- Fix potential panic when debug request captures are enabled by @theckman in #443
- Fixes memory leak by @attilakunelwood in #453
- Prevent leak on error responses by @ChuckCrawford in #454
- This project has a new primary branch. Long live the
main
branch!
Breaking Changes
- Fix unmarshaling error with AlertGroupingParameters timeout by @mjlshen in #459
- Fix parsing bug for AlertGroupingParameters by @mjlshen in #448
- Fix ResponderRequest regression by @ehlerorngard in #452
New Contributors
- @jaimegago made their first contribution in #439
- @mjlshen made their first contribution in #434
- @attilakunelwood made their first contribution in #453
- @ChuckCrawford made their first contribution in #454
- @ehlerorngard made their first contribution in #452
Full Changelog: v1.5.0...1.6.0
Milestone: Milestone 1.6.0