[BUILD-741] Generate list of updates for RNs Created: 05/Apr/22 Updated: 20/Oct/22 Resolved: 20/Oct/22 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Epic Link: | Renovate | ||||||||
| Description |
|
RNs currently resolve the list of updates by looking up Jira issues for a specific BOMs version, see: https://git.magnolia-cms.com/projects/INTERNAL/repos/magnolia-mgmt/browse/src/main/java/info/magnolia/mgmt/ReleaseNotesService.java#85-90 As the way to go with Renovate is to no longer create an issue for every single update, we will need to update the above code by computing which dependencies Renovate has commited to a specific repository instead. If in need of material to share with customers re: a specific security issue coming from a 3rd party library, we can always give them a reference to a PR or commit. |