Please please please, if you are going to approve Dependabot PRs, the task is not complete until you update changes.xml; especially for runtime dependencies!
For the benefit of our users (and ourselves) and transparency, we need to track these changes. I can understand the laziness around not bothering for test or build dependencies, but runtime changes MUST be documented IMO. Personally, I just document it all, it makes for a simpler process (for me.) Thank you, Gary ---------- Forwarded message --------- From: <ki...@apache.org> Date: Thu, Sep 10, 2020 at 1:33 AM Subject: [commons-imaging] 01/01: Merge pull request #96 from apache/dependabot/maven/commons-io-commons-io-2.8.0 To: comm...@commons.apache.org <comm...@commons.apache.org> This is an automated email from the ASF dual-hosted git repository. kinow pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/commons-imaging.git commit 5ab6b2059f9201fdec1d73991f6ffce65ae18e79 Merge: 4ba419d 7fb71bd Author: Bruno P. Kinoshita <ki...@users.noreply.github.com> AuthorDate: Thu Sep 10 17:27:24 2020 +1200 Merge pull request #96 from apache/dependabot/maven/commons-io-commons-io-2.8.0 Bump commons-io from 2.7 to 2.8.0 pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
