This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/junit-junit-4.13.2
in repository https://gitbox.apache.org/repos/asf/commons-exec.git.
discard c12396f Bump junit from 4.13.1 to 4.13.2
add c911942 Add CODE_OF_CONDUCT.md
add d533d46 Build on Windows and macOS too.
add 3ae449b Assume testExec65WithSudoUsingShellScript will fail on GitHub.
add 6c3f2b5 Update JApiCmp to allow builds to run on Java 17.
add 9b8f5e3 Bump junit from 4.13.1 to 4.13.2
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 (c12396f)
\
N -- N -- N refs/heads/dependabot/maven/junit-junit-4.13.2
(9b8f5e3)
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 | 1 +
SECURITY.md => CODE_OF_CONDUCT.md | 2 +-
pom.xml | 1 +
src/test/java/org/apache/commons/exec/issues/Exec65Test.java | 2 ++
4 files changed, 5 insertions(+), 1 deletion(-)
copy SECURITY.md => CODE_OF_CONDUCT.md (83%)
