Bump junit-pioneer from 0.5.6 to 1.0.0 #2846
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
the
dependencies
dependabot
bot
force-pushed
the
dependabot/maven/org.junit-pioneer-junit-pioneer-1.0.0
branch
from
afffc0e
to
25bb3b9
Compare
|
@dependabot rebase |
dependabot
bot
force-pushed
the
dependabot/maven/org.junit-pioneer-junit-pioneer-1.0.0
branch
from
25bb3b9
to
154389a
Compare
|
Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
|
See also junit-pioneer/junit-pioneer#343 That issue describes this issue -- tests failing, but the build continuing (the only visible symptom being a drop in coverage unless inspecting the build logs for the warning). That issue also indicates to make use of the junit BOM ("bill of materials"), but I'm not exactly sure how that works so shall do further research/get a better understanding. Note the warning, not an error (thus build completes, despite the failure) in this build using v1.0.0: https://github.com/javaparser/javaparser/pull/2846/checks?check_run_id=1368951279#step:6:5017 Basically the same problem is found when upgrading to v0.9.2 : https://github.com/MysterAitch/javaparser/pull/160/checks?check_run_id=1369195131#step:6:6579 |
Bumps [junit-pioneer](https://github.com/junit-pioneer/junit-pioneer) from 0.5.6 to 1.0.0. - [Release notes](https://github.com/junit-pioneer/junit-pioneer/releases) - [Changelog](https://github.com/junit-pioneer/junit-pioneer/blob/master/docs/release-notes.md) - [Commits](junit-pioneer/junit-pioneer@v0.5.6...v1.0.0) Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/maven/org.junit-pioneer-junit-pioneer-1.0.0
branch
from
154389a
to
2909237
Compare
|
Superseded by #2944. |
dependabot
bot
deleted the
dependabot/maven/org.junit-pioneer-junit-pioneer-1.0.0
branch
This was referenced Mar 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps junit-pioneer from 0.5.6 to 1.0.0.
Release notes
Sourced from junit-pioneer's releases.
... (truncated)
Changelog
Sourced from junit-pioneer's changelog.
... (truncated)
Commits
74623a91.0.0 release (previous 0.9.2) + release notes updated [ci skip]2d95093Update version to 1.0.0 (#352 / #353)2764bc7Update contribution guideline to non-zero major versions (#225 / #333)9fe8b17Add note in documentation to use JUnit's BOM (#343 / #351)9eb8e26Introduce @CartesianProductText extension (#68 / #321)7950e65Clean up module build (#314 / #350)ffc5506Limit docs code snippets line length to max 60 chars (#317 / #318)5c47d6cRemove @TempDir extension (#277 / #327)ce5fc530.9.2 release (previous 0.9.1) + release notes updated [ci skip]61f8839Use junit-bom to set JUnit dependency versions (#343 / #346)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)