You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just to inform you that you introduced a BC change in a bugfix version.
We switched from v6.0.3 to v6.0.9 as our constraint does not fix the bugfix version, and this resulted in issues in our app.
PostmarkClient::getSuppressions saw its return type change from PostmarkSuppressionRequestList to PostmarkSuppressionList, which internally creates PostmarkSuppression and not PostmarkSuppressionRequestResult anymore.
Type-hinting we had in place failed, and properties of these objects are not the same, even if we only relied on the emailAddress, so changing the type-hint allowed us to easily fix the issue.
Are you following a semver policy or can any release on your end include other BCs?
The text was updated successfully, but these errors were encountered:
Hello,
Just to inform you that you introduced a BC change in a bugfix version.
We switched from v6.0.3 to v6.0.9 as our constraint does not fix the bugfix version, and this resulted in issues in our app.
PostmarkClient::getSuppressions
saw its return type change fromPostmarkSuppressionRequestList
toPostmarkSuppressionList
, which internally createsPostmarkSuppression
and notPostmarkSuppressionRequestResult
anymore.Type-hinting we had in place failed, and properties of these objects are not the same, even if we only relied on the emailAddress, so changing the type-hint allowed us to easily fix the issue.
Are you following a semver policy or can any release on your end include other BCs?
The text was updated successfully, but these errors were encountered: