Details
-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
The ReleaseNotesService computes release notes after each released based on Git data. However, since we introduced Renovate, we don't necessarily create one ticket per each Renovate PR. Nevertheless, it would be nice to also include those upgrades in the release notes.
- first, the appropriate branch's current SHA1 must be resolved: http://git.magnolia-cms.com/rest/api/latest/projects/BUILD/repos/boms/branches
- then, using the above hash, commits by 'Renovate Bot' must be compiled from the following endpoint (beware paging): http://git.magnolia-cms.com/rest/api/latest/projects/BUILD/repos/boms/commits/44b24f1255948c90c74c96a33d0d3d5b2295915e
- however, only commits since the last release must be included. Therefore, the SHA1 associated with the latest release's tag must be found: http://git.magnolia-cms.com/rest/api/latest/projects/BUILD/repos/boms/tags
- ... and used as the beginning limit of the commit list
- finally, an output format in line with current RNs must be suggested & discussed with the documentation team. Most probably each upgrade should link to the commit on Git (rather than the Jira issue). See for instance: https://docs.magnolia-cms.com/product-docs/6.2/Releases/Release-notes-for-Magnolia-CMS-6.2.24.html#_third_party_library_updates
Checklists
Acceptance criteria
Attachments
Issue Links
- is duplicated by
-
BUILD-741 Generate list of updates for RNs
-
- Closed
-