Update dependency com.teamscale:teamscale-client to v32

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.teamscale:teamscale-client	29.0.0 -> 32.5.0

---

Release Notes

cqse/teamscale-jacoco-agent (com.teamscale:teamscale-client)

v32.5.0

Compare Source

• [feature] teamscale-maven-plugin: Added the upload-coverage goal which automatically uploads JaCoCo reports to Teamscale.

v32.4.2

Compare Source

• [fix] agent: The agent crashed while starting on some machines with "cannot construct instances of" errors

v32.4.1

Compare Source

• [fix] agent: The agent crashed while starting on some machines with "cannot construct instances of" errors

v32.4.0

Compare Source

• [feature] agent: Added stable support for Java 21 and experimental support for Java 22
• [fix] agent: Produce more helpful error results in case a service call to Teamscale fails while handling an HTTP call
• [fix] teamscale-maven-plugin: The same uniform paths were extracted for tests that have the same name in a Cucumber feature file

v32.3.1

Compare Source

• Re-release because of failing publishing process
• • impacted-test-engine: Failed requests to Teamscale did result in unreadable error message
  • [feature] teamscale-maven-plugin: Automatically find open port for coverage collection.
  • [fix] teamscale-maven-plugin: Same uniform path was extracted for Cucumber scenario outlines which do not have their parameters in the title

v32.2.0

Compare Source

• [feature] agent: Previously unsuccessful coverage uploads are now automatically retried upon agent restart
• [fix] teamscale-maven-plugin: Fix uniform path and cluster ID extraction for cucumber pre 7.11.2

v32.1.1

Compare Source

Re-release incomplete 32.1.0 release

v32.0.0

Compare Source

• [breaking] teamscale-gradle-plugin: Removed usage of deprecated Gradle APIs
  • teamscale.agent.destinationProperty type has changed from Property<File> to DirectoryProperty
  • teamscale.agent.setDestination(destination) parameter type has changed from Property<File> to Provider<Directory>
• [fix] agent: Discovery of unsupported class file versions will no longer lead to a crash, but will be logged instead
• [breaking] tia-runlisteners: Requires JUnit 5.10.0 now
• [feature] agent: Added support for Java 19, 20 and experimental support for 21
• [fix] agent: Attaching the agent in testwise mode to a JBoss Wildfly server caused a crash

v31.0.0

Compare Source

• [breaking] Replaced teamscale-git-properties-jar with git-properties-jar. Jars/Wars/Ears/Aars provided with this option will now also be searched recursively for git.properties files except you set search-git-properties-recursively=false.
• [feature] support full mode of the Maven git-commit-id plugin.
• [fix] Providing multiple include pattern in the maven plugin resulted in no coverage being collected

v30.1.1

Compare Source

• [fix] teamscale-gradle-plugin: Warnings were logged during test execution (WARNING: JAXBContext implementation could not be found. WADL feature is disabled., WARNING: A class javax.activation.DataSource for a default provider)

v30.1.0

Compare Source

• [feature] The option tiamode has now an additional choice disk to dump testwise coverage as JSON to the output folder.
• [feature] teamscale-maven-plugin: The configuration options runAllTests, runImpacted, and tiamode are now available
• [fix] impacted-test-engine: Mixed test results for dynamically generated tests were incorrectly summarized
• [fix] The option ignore-uncovered-classes did not filter out empty interface nodes from the XML report
• [fix] teamscale-gradle-plugin: The plugin failed to log the No class files found in the given directories! error message

v30.0.2

Compare Source

• [fix] teamscale-gradle-plugin: Reports uploaded by teamscaleReportUpload ended up in wrong partition
• [fix] impacted-test-engine: Failure when no tests were impacted

v30.0.1

Compare Source

• [fix] report-generator: Fixed Gradle module metadata which resulted in Could not find org.jacoco.agent-0.8.8-runtime

v30.0.0

Compare Source

• [breaking change] teamscale-maven-plugin: Made plugin compatible with surefire 3.0.0. Replace the teamscale-surefire-provider dependency with impacted-test-engine in your pom.xml files.
• [feature] teamscale-gradle-plugin, teamscale-maven-plugin: Added ability to pass excluded test engines to impacted test engine
• [fix] teamscale-maven-plugin: Testwise coverage uploads were performed per test cluster instead of one upload after all tests
• [fix] teamscale-gradle-plugin, teamscale-maven-plugin: Impacted tests were requested once for each test engine
• [fix] teamscale-gradle-plugin, teamscale-maven-plugin: Execution of impacted tests failed when test names were unstable i.e. parameterized tests with parameters that are not serializeable

v29.1.3

Compare Source

• [fix] http control server was not correctly shut down after the tests ended

v29.1.2

Compare Source

• [fix] teamscale-maven-plugin: Partition was not correctly provided to the impacted test engine
• [fix] tia-client: Semicolons in test names were not correctly sent to the Teamscale JaCoCo Agent

v29.1.1

Compare Source

• [fix] teamscale-gradle-plugin, teamscale-maven-plugin, teamscale-jacoco-agent: Tooling did not provide a way to set the partial flag

v29.1.0

Compare Source

• [feature] teamscale-gradle-plugin: Allow parallel test execution with testwise coverage collection
• [fix] teamscale-gradle-plugin: Verify that maxParallelForks is 1
• [fix] impacted-test-engine: Provide sane fallback for non-supported test engines

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.