Bump com.approvaltests:approvaltests from 18.7.1 to 20.0.0

[dependabot]

Bumps com.approvaltests:approvaltests from 18.7.1 to 20.0.0.

Release notes

Sourced from com.approvaltests:approvaltests's releases.

Removal of EnvironmentAwareReporter

This is a breaking change.

When you call Reporter.report(received, approved) it now returns if it was successful. This makes the java architecture more consistent with other implementations and allows us to determine when something should have worked but it didn't.

It should not affect you unless you've written a custom implementation of ApprovalFailureReporter.

Information on why and how to upgrade can be found here.

Exceptions and Help messages on duplicate verify() calls.

ApprovalTests only wants one call to verify() per test. There are ways to go around this but if you call verify where it would want the exact same file name twice, it will now throw an exception. This will make it easier for people to not be confused as most other testing frameworks allow you to put multiple assertions in the same test.

Backwards compatibility

There are some situations where you want to check that two different processes produce the same result. Calling verify multiple times in the same test can be a way to do this. If you want to do that, we have provided two calls:

• Approvals.settings().allowMultipleVerifyCallsForThisClass()
• Approvals.settings().allowMultipleVerifyCallsForThisMethod()

Commits

• cbf0b61 . e drop test runs on jdk 22-ea because of: Error: Could not find satisfied v...
• 843f04c . e cancel existing pipeline runs if a new one started
• 40b67d9 . d Update RemovingEnvironmentAwareReporter.md
• c74f7b6 . d Update RemovingEnvironmentAwareReporter.md
• 50d4844 . d Update RemovingEnvironmentAwareReporter.md
• 482e3b1 * d fix mermaid diagram to render
• 02b0b46 d updated markdown snippets
• 5442577 * d explain the removal of EnvironmentAwareReporter
• a426a5c ! F delete concept of EnvironmentAwareReporter
• e8e859c ! F Reporters now return success
• Additional commits viewable in compare view

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 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 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)

[dependabot]

Superseded by #23.