Bump ru.vyarus:spock-junit5 from 1.4.1 to 2.1.0

[dependabot]

Bumps ru.vyarus:spock-junit5 from 1.4.1 to 2.1.0.

Release notes

Sourced from ru.vyarus:spock-junit5's releases.

2.1.0

• Add @DebugJunitExtensions annotation to print registered and called junit extensions
• Add @IgnoreJunitExtensions annotation to ignore some declared junit extensions (to resolve collisions like with spock-spring)
• spock-spring compatibility: junit SpringExtension automatically ignored (spock manages spring context and all other junit extensions will work)

2.0.1

• Fix github repository links in POM

2.0.0

• Junit 6.0 compatibility
  • Apply context API changes
  • Storage implementation completely updated (based on the new jupiter implementation to behave exactly the same)
• [BREAKING] Drop java 8-16 support (junit 6 dropped support for them)
• [BREAKING] Artifact name changed: spock-junit6
  • version is not reset to 1.0 to preserve cross-versioning and to avoid usage mistakes
  • a different artifact name would avoid dependabot updates spamming for incompatible junit versions
• Fix spock 2.4 compatibility: spock 2.4 moved FEATURE_EXECUTION before INITIALIZATION, so now JunitExtensionSupport.getStore(,) simply returns available context without trying to guess

1.5.0

• Add @DebugJunitExtensions annotation to print registered and called junit extensions
• Add @IgnoreJunitExtensions annotation to ignore some declared junit extensions (to resolve collisions like with spock-spring)
• spock-spring compatibility: junit SpringExtension automatically ignored (spock manages spring context and all other junit extensions will work)

Changelog

Sourced from ru.vyarus:spock-junit5's changelog.

2.1.0 (2026-02-17)

• Add @​DebugJunitExtensions annotation to print registered and called junit extensions
• Add @​IgnoreJunitExtensions annotation to ignore some declared junit extensions (to resolve collisions like with spock-spring)
• spock-spring compatibility: junit SpringExtension automatically ignored (spock manages spring context and all other junit extensions will work)

2.0.1 (2026-02-06)

• Fix github repository links in POM

2.0.0 (2026-02-05)

• Junit 6.0 compatibility
  • Apply context API changes
  • Storage implementation completely updated (based on the new jupiter implementation to behave exactly the same)
• [BREAKING] Drop java 8-16 support (junit 6 dropped support for them)
• [BREAKING] Artifact name changed: spock-junit6
  • version is not reset to 1.0 to preserve cross-versioning and to avoid usage mistakes
  • a different artifact name would avoid dependabot updates spamming for incompatible junit versions
• Fix spock 2.4 compatibility: spock 2.4 moved FEATURE_EXECUTION before INITIALIZATION, so now JunitExtensionSupport.getStore(,) simply returns available context without trying to guess

1.4.0 (2026-02-04)

• Junit 5.12 compatibility
  • Implement missed extension context API methods
  • The new PreInterruptCallback callback is not supported (triggered by a not supported @​Timeout extension)
• Junit 5.13 compatibility
  • Implement missed extension context API methods
  • New callbacks BeforeClassTemplateInvocationCallback, AfterClassTemplateInvocationCallback and ClassTemplateInvocationContextProvider not supported (no templates in spock)
• Junit 5.14 compatibility
  • Implement missed extension context API methods
• Add AutoCloseable values support for storage (CloseableResource is deprecated)

Note: there is no need for separate releases because only new methods were added

1.3.0 (2026-02-03)

• Junit 5.11 compatibility:
  • @​ExtendWith on a non-static field now participate in beforeAll/afterAll;
  • static extension fields are registered before non-static fields (junit behavior change fixing extensions order)
• Add support for LifecycleMethodExecutionExceptionHandler (for spock setupSpec, setup etc.)

1.2.0 (2022-11-25)

• Add root (engine-level) context to be able to use global storage in extensions (#44) (context.getRoot().getStore())

1.1.0 (2022-09-08)

• Update to junit 5.9 (spock 2.2 compatibility)
  • added ExecutableInvoker support (might be obtained through extension context (getExecutableInvoker()) in order to manually call constructors and methods with registered ParameterResolver extensions)

... (truncated)

Commits

• db37084 [Gradle Release Plugin] - pre tag commit: '2.1.0'.
• 6324903 update docs
• d3402da bump version
• be2d806 remove warning in spock-spring detection message
• 936fad2 Merge pull request #91 from xvik/dependabot/gradle/org.junit-junit-bom-6.0.3
• ee80102 Bump org.junit:junit-bom from 6.0.2 to 6.0.3
• f809d2f add @​IgnoreJunitExtensions annotation to ignore some declared junit extension...
• 6cea7cc add @DebugJunitExtensions annotation to print registered and called junit e...
• d8bd898 [Gradle Release Plugin] - new version commit: '2.0.2-SNAPSHOT'.
• c09830f [Gradle Release Plugin] - pre tag commit: '2.0.1'.
• 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 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)