This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/github_actions/actions/cache-2.1.7 in repository https://gitbox.apache.org/repos/asf/commons-dbcp.git.
discard 22d15a5 Bump actions/cache from 2.1.6 to 2.1.7 add 5d5b5f3 Bump mockito-core from 4.0.0 to 4.2.0 (#152) add 1fb4c33 Bump mockito-core from 4.0.0 to 4.2.0 #152. add bcf722d Drop obsolete Travis build. add f8eb730 Bump spotbugs from 4.4.1 to 4.5.2 (#151) add 4f41bfc Bump spotbugs from 4.4.1 to 4.5.2 #151. add 4e44988 Bump actions/checkout from 2.3.5 to 2.4.0 (#143) add 85d5936 Bump actions/cache from 2.1.6 to 2.1.7 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (22d15a5) \ N -- N -- N refs/heads/dependabot/github_actions/actions/cache-2.1.7 (85d5936) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .github/workflows/maven.yml | 2 +- .travis.yml | 25 ------------------------- pom.xml | 4 ++-- src/changes/changes.xml | 4 ++-- 4 files changed, 5 insertions(+), 30 deletions(-) delete mode 100644 .travis.yml