Integration release notes should explain changes through user actions
“Adapter fixed” tells little to someone updating a working client. For your SimAggregator integration, describe visible behavior: what happened before, what happens now, and whether the user must do anything after upgrading. An internal issue name can remain a link.
If page recovery changed, explain whether existing local tasks remain accessible and which limitations remain. Do not present an improvement in your own interface as a change in the external platform's rules. State the scope: client version, affected screen, and required setting.
Highlight items requiring attention, such as a new local file format, a configuration check, or a compatibility limit. Ask a colleague on the previous version to follow the instructions. They should understand the upgrade path without a private explanation from the author.
Publish translated notes with the main text, especially when paid actions behave differently. Do not leave an old retry recommendation in one language. Useful release notes can be short while still answering what changes in the person's work and how they can verify a successful upgrade.