janhoy commented on PR #4453: URL: https://github.com/apache/solr/pull/4453#issuecomment-4557121827
> Also, do we really need to track dependency updates as part of the changelog thing? Probably a fine discussion to have as well, although a separate one... We used to have it as a separate RM task to week out the final CHANGES.txt including hunting down updates. It is very very common to report in a changelog what dependencies were upgraded as part of a release. Some releases for some tools do ONLY contain dependency upgrades. I think you ask this question due to our relatively large volume of dependencies, thus also a large volume of upgrades. And I agree it makes sense to filter out repeated dep-upgrade lines for the same release. Noone cares if commons-io was upgraded twice before we had a release :) This issue, however, is to harden the process we already have. Thanks for the review. I'm not aware of a way to "unit" test workflows. Once we merge this we'll see whether it works or not. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
