You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dependabot@commons.apache.org by "dependabot[bot] (via GitHub)" <gi...@apache.org> on 2026/09/13 08:38:39 UTC
[PR] Bump de.mannodermaus.junit5:android-test-core from 1.4.0 to 2.0.1 in /android-tests [commons-secure-xml]
dependabot[bot] opened a new pull request, #93:
URL: https://github.com/apache/commons-secure-xml/pull/93
Bumps [de.mannodermaus.junit5:android-test-core](https://github.com/mannodermaus/android-junit5) from 1.4.0 to 2.0.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/mannodermaus/android-junit5/releases">de.mannodermaus.junit5:android-test-core's releases</a>.</em></p>
<blockquote>
<h2>2.0.1</h2>
<p>This release fixes an error with the <a href="https://docs.gradle.org/current/userguide/publishing_gradle_module_metadata.html">Gradle Module Metadata</a> published alongside the instrumentation libraries. In particular, the artifact ID of the transitive dependency on <code>android-test-core</code> from <code>android-test-compose</code> was broken. This is remedied now.</p>
<h2>2.0.0</h2>
<p>Happy New Year! 2026 marks the ten year anniversary of this project, as I released the very first version all the way back in September 2016. Time <em>flies</em>, man. Therefore, please join me in celebration and welcome this new year by bumping both the plugin and instrumentation to a whole new major version, and a whole new name. <code>android-junit5</code> becomes <code>android-junit-framework</code>!! ✨</p>
<p>I have changed the versioning scheme before and I'm not afraid to do it again. Going forward, this project is no longer tightly coupled to a particular version of the JUnit Framework. Furthermore, both pieces of <code>android-junit-framework</code> are now compatible with JUnit 5 <strong>and</strong> 6. (Note that for JUnit 6, you need a baseline of Java 17, so your Android devices need to run API 35 or newer to make this happen.) Furthermore, there is a behavioral change when it comes to skipping vs failing on unsupported devices. Please find the gist below.</p>
<p>I hope that the project will mature into a state where people can choose their preferred JUnit freely. Inspired by the great documentations of Zac and co., one of the next milestones on my list is a revamped documentation for the project. I also finally want to nuke the awful wiki section (it's outdated AF) and move all documentation to a central place.</p>
<p>Stay tuned, and all the best for a successful 2026.
– Marcel / mannodermaus ❤️</p>
<hr />
<h2>Changelog (Plugin)</h2>
<ul>
<li>Update to Kotlin 2.3</li>
<li>Internal: Replace deprecated <code>OutputDirectoryProvider</code> with its correct replacement</li>
<li>Support instrumentation with JUnit 5 and 6 (the plugin will choose the correct runtime accordingly)</li>
<li>Introduce <code>de.mannodermaus.android-junit</code> as the new plugin ID</li>
<li>New: Control behavior of test execution on unsupported devices via <code>instrumentationTests.behaviorForUnsupportedDevices</code>
<ul>
<li>"Fail": Throw an exception and fail test execution (<strong>this is the new default</strong>)</li>
<li>"Skip": Skip tests and mark them as ignored (<strong>this is the old behavior</strong>)</li>
</ul>
</li>
</ul>
<h2>Changelog (Instrumentation)</h2>
<ul>
<li>Removed deprecated <code>runComposeTest</code> API from <code>ComposeExtension</code></li>
<li>Update to Kotlin 2.3</li>
<li>Update to Compose 1.10</li>
<li>Support instrumentation with JUnit 5 and 6 (the plugin will choose the correct runtime accordingly)</li>
<li>Avoid error when a client doesn't include junit-jupiter-params on the runtime classpath</li>
<li>New: Instead of silently skipping tests when running on unsupported devices, fail test execution via configuration parameter <code>de.mannodermaus.junit.unsupported.behavior</code></li>
</ul>
<h2>Plugin 1.14.0.0</h2>
<p>This release brings compatibility with JUnit 5.14.0. Most notably, there is a breaking change inside of that version of JUnit 5, meaning that if you want to use it, you will need to keep this plugin in sync as well.</p>
<h2>Plugin 1.13.4.0</h2>
<p>This release brings compatibility with JUnit 5.13.4. As with the last releases since 1.13.2.0, we restrict all remaining usages of the old plugin and variant API (e.g. BaseExtension and friends). This was always restricted to users of the Jacoco integration, but now there should be no problems for those users.</p>
<p>However, in response to the move to the new DSL, Jacoco integration is effectively deprecated until further notice if you are using AGP 9.0.0-alpha04 or newer. We will see if Google reintroduces some of the APIs that we still needed to rely on the old DSL for, but as of now the integration is disabled and a warning is logged.</p>
<h2>Plugin 1.13.3.0</h2>
<p>This release brings compatibility with JUnit 5.13.3. As with the last one, we restrict all remaining usages of the old plugin and variant API (e.g. BaseExtension and friends). This was always restricted to users of the Jacoco integration, but now there should be no problems for those users.</p>
<p>However, in response to the move to the new DSL, Jacoco integration is effectively deprecated until further notice if you are using AGP 9.0.0-alpha04 or newer. We will see if Google reintroduces some of the APIs that we still needed to rely on the old DSL for, but as of now the integration is disabled and a warning is logged.</p>
<h2>Plugin 1.13.2.0</h2>
<p>This release of the plugin brings compatibility with JUnit 5.13.2. It is also the first release to make some advancements towards Android Gradle Plugin 9.x. We restrict all remaining usages of the old plugin and variant API (e.g. <code>BaseExtension</code> and friends). This was always restricted to users of the Jacoco integration, but now there should be no problems for those users.</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/6016756c6c29aa8540468e80965e35465e90e301"><code>6016756</code></a> Plugin 2.0.1</li>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/af66349ff278085df6cb9b54a9fbc728cb4c3878"><code>af66349</code></a> Instrumentation 2.0.1</li>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/c3cd775dcc39a38a12b6a6367ff94be6b2dbba8e"><code>c3cd775</code></a> Use correct artifactIds in GMM, too (<a href="https://redirect.github.com/mannodermaus/android-junit5/issues/405">#405</a>)</li>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/e4dcfc939afc4862fda8dd65794f5e21a2e76822"><code>e4dcfc9</code></a> Force correct JUnit BOM for our own internal instrumentation tests</li>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/2dcf3051b9091f08f37de6c5894622f234890eab"><code>2dcf305</code></a> Replace temp config param in instrumentation with the proper replacement</li>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/feb3919eb0d367244602f85c7851ffdc66009dfd"><code>feb3919</code></a> Replace deprecated androidDependencies task in CI</li>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/592eadcff970633176e303f33b4a2bdee273cfd5"><code>592eadc</code></a> Update plugin ID in changelog</li>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/97ace63d29bc31f5c72a95bd3deb1b943d35a92a"><code>97ace63</code></a> Tweak release process again</li>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/9db3b52de7176629a17359e58a92bab937313412"><code>9db3b52</code></a> Happy New Year! Update readme & prepare next version</li>
<li><a href="https://github.com/mannodermaus/android-junit-framework/commit/1f67f0f8802091b7523a8fe5cf0320b24aaeeead"><code>1f67f0f</code></a> Plugin 2.0.0</li>
<li>Additional commits viewable in <a href="https://github.com/mannodermaus/android-junit5/compare/plugin-1.4.0.0...plugin-2.0.1">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@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)
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dependabot-unsubscribe@commons.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Bump de.mannodermaus.junit5:android-test-core from 1.4.0 to 2.0.1 in /android-tests [commons-secure-xml]
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz merged PR #93:
URL: https://github.com/apache/commons-secure-xml/pull/93
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org