Open inFocus7 opened 1 year ago
Have a WIP PR for this. While writing the PRs description, the possibility of DEPENDENCY_BUMP
s being downgraded hit me, and this approach may not be the best approach.
A different path forward which may be a better approach to show the latest dependency updates, is to automate through a GitHub Action/Workflow... [On PR Push | in a queued concurrent group, so there's no action clashing]:
changelog.yaml
for dependency bumpsThrough that different path, we could leave the code here as-is, since the action will take care of keeping the important dependency bumps before we generate the release changelog.
When listing the dependency bumps in our changelogs, we should sanitize them to only output the latest semver bump for a specific repo/dependency.
For example, in Gloo OSS release v1.15.0-beta5 there are two dependency bumps listed for
solo-io/envoy-gloo
although the important bump for readers of changelog is the latest bump of those two.Rough logic for this would be updating the
renderDependencyBumps
function to be something like:relevant code
Definition of Done to be discussed but at the very least