Skip to content

Bump junit from 4.13-rc-1 to 4.13.1 - #6

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/maven/junit-junit-4.13.1
Closed

Bump junit from 4.13-rc-1 to 4.13.1#6
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/maven/junit-junit-4.13.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 13, 2020

Copy link
Copy Markdown

Bumps junit from 4.13-rc-1 to 4.13.1.

Release notes

Sourced from junit's releases.

JUnit 4.13.1

Please refer to the release notes for details.

JUnit 4.13

Please refer to the release notes for details.

JUnit 4.13 RC 2

Please refer to the release notes for details.

Changelog

Sourced from junit's changelog.

Summary of changes in version 4.13.1

Rules

Security fix: TemporaryFolder now limits access to temporary folders on Java 1.7 or later

A local information disclosure vulnerability in TemporaryFolder has been fixed. See the published security advisory for details.

Test Runners

[Pull request #1669:](junit-team/junit#1669) Make FrameworkField constructor public

Prior to this change, custom runners could make FrameworkMethod instances, but not FrameworkField instances. This small change allows for both now, because FrameworkField's constructor has been promoted from package-private to public.

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 13, 2020
@r4m-glib-pakharenko
r4m-glib-pakharenko force-pushed the dependabot/maven/junit-junit-4.13.1 branch from 0d788b3 to 8008e72 Compare August 13, 2026 14:05
@github-actions

Copy link
Copy Markdown

Uh Oh

It seems that your pull request doesn't pass conventional commit validation

Don't worry! This guide will help you to fix this issue and avoid it in future!

  • Please check conventional commit specification and tips how to write perfect messages
  • If you are using IntelliJ IDEA, please take a look at special plugin
  • In order to fix your commit messages you should create new pull request from another branch, force push is not allowed. You can do it in IntelliJ IDEA using this guide or using git cli and that guide. This pull request will be closed automatically.

@github-actions github-actions Bot closed this Aug 13, 2026
@github-actions

Copy link
Copy Markdown

Uh Oh

It seems that your pull request doesn't pass conventional commit validation

Don't worry! This guide will help you to fix this issue and avoid it in future!

  • Please check conventional commit specification and tips how to write perfect messages
  • If you are using IntelliJ IDEA, please take a look at special plugin
  • In order to fix your commit messages you should create new pull request from another branch, force push is not allowed. You can do it in IntelliJ IDEA using this guide or using git cli and that guide. This pull request will be closed automatically.

@dependabot @github

dependabot Bot commented on behalf of github Aug 13, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/maven/junit-junit-4.13.1 branch August 13, 2026 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants