fix(deps): update dependency jacoco to v0.8.12

[pleo-bot-renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jacoco (source)	0.8.7 -> 0.8.12

---

Release Notes

jacoco/jacoco (jacoco)

v0.8.12: 0.8.12

New Features

• JaCoCo now officially supports Java 22 (GitHub #​1596).
• Experimental support for Java 23 class files (GitHub #​1553).

Fixed bugs

• Branches added by the Kotlin compiler for functions with default arguments and having more than 32 parameters are filtered out during generation of report (GitHub #​1556).
• Branch added by the Kotlin compiler version 1.5.0 and above for reading from lateinit property is filtered out during generation of report (GitHub #​1568).

Non-functional Changes

• JaCoCo now depends on ASM 9.7 (GitHub #​1600).

v0.8.11: 0.8.11

New Features

• JaCoCo now officially supports Java 21 (GitHub #​1520).
• Experimental support for Java 22 class files (GitHub #​1479).
• Part of bytecode generated by the Java compilers for exhaustive switch expressions is filtered out during generation of report (GitHub #​1472).
• Part of bytecode generated by the Java compilers for record patterns is filtered out during generation of report (GitHub #​1473).

Fixed bugs

• Instrumentation should not cause VerifyError when the last local variable of method parameters is overridden in the method body to store a value of type long or double (GitHub #​893).
• Restore exec file compatibility with versions from 0.7.5 to 0.8.8 in case of class files with zero line numbers (GitHub #​1492).

Non-functional Changes

• jacoco-maven-plugin now requires at least Java 8 (GitHub #​1466, #​1468).
• JaCoCo build now requires at least Maven 3.5.4 (GitHub #​1467).
• Maven 3.9.2 should not produce warnings for jacoco-maven-plugin (GitHub #​1468).
• JaCoCo build now requires JDK 17 (GitHub #​1482).
• JaCoCo now depends on ASM 9.6 (GitHub #​1518).

v0.8.10: 0.8.10

Fixed bugs

• Agent should not require configuration of permissions for SecurityManager outside of its codeBase (GitHub #​1425).

v0.8.9: 0.8.9

New Features

• JaCoCo now officially supports Java 19 and 20 (GitHub #​1371, #​1386).
• Experimental support for Java 21 class files (GitHub #​1386).
• Add parameter to include the current project in the report-aggregate Maven goal (GitHub #​1007).
• Component accessors generated by the Java compilers for records are filtered out during generation of report. Contributed by Tesla Zhang (GitHub #​1393).

Fixed bugs

• Agent should not open java.lang package to unnamed module of the application class loader (GitHub #​1334).

Non-functional Changes

• JaCoCo now depends on ASM 9.5 (GitHub #​1299, #​1368, #​1416).
• JaCoCo build now requires JDK 11 (GitHub #​1413).

v0.8.8: 0.8.8

New Features

• JaCoCo now officially supports Java 17 and 18 (GitHub #​1282, #​1198).
• Experimental support for Java 19 class files (GitHub #​1264).
• Part of bytecode generated by the Java compilers for assert statement is filtered out during generation of report (GitHub #​1196).
• Branch added by the Kotlin compiler version 1.6.0 and above for "unsafe" cast operator is filtered out during generation of report (GitHub #​1266).
• Improved support for multiple JaCoCo runtimes in the same VM (GitHub #​1057).

Fixed bugs

• Fixed NullPointerException during filtering (GitHub #​1189).
• Fix range for debug symbols of method parameters (GitHub #​1246).

Non-functional Changes

• JaCoCo now depends on ASM 9.2 (GitHub #​1206).
• Messages of exceptions occurring during analysis or instrumentation now include JaCoCo version (GitHub #​1217).

---

Configuration

📅 Schedule: Branch creation - "after 8am and before 4pm every weekday" in timezone CET, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[pleo-bot-renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[DimitrisKaramanis]

This PR is going to be closed automatically, because it is created by a deprecated Renovate bot. A new PR will be created by the new renovate process, just sit back and relax. :)