Allure Gradle plugin unnecessary triggers tests execution

[Toparvion]

Hello, Allure Community!
I'm trying to use Allure Gradle Plugin v2.9.4 with my Java application (Liberica JDK 1.8.0_372) on Gradle 6.9.

After adding the plugin (in Kotlin DSL):

plugins {
    id("io.qameta.allure") version "2.9.4"
}

and invoking e.g. gradle assemble lifecycle task I see that unit tests get executed though they should not (and were not before Allure).

Looking at the --info logging output of Gradle, I see that the test task is added to the execution list at the configuration stage:

> Configure project :linkserver-install
Evaluating project ':linkserver-install' using build file …
…
Selected primary task ':linkserver-install:assemble' from project :linkserver-install
allure-gradle: added dependency io.qameta.allure:allure-junit4:2.13.9 to runtime scope of junit:junit:4.13.2
allure-gradle: added dependency io.qameta.allure:allure-junit4-aspect:2.13.9 to runtime scope of junit:junit:4.13.2
…
Tasks to be executed: [task ':linkserver-install:compileJava', task … ':linkserver-install:test', task … ':linkserver-install:assemble']
Tasks that were excluded: []
All projects evaluated.

And analyzing the Build Scan, I see that:

The task was not up-to-date because of the following reasons:
One or more additional actions for task ':linkserver-install:test' have changed.

However, I don't know what "additional actions" the scan means and how to figure them out.

Could anyone help to figure out the root cause of this behavior?

[Toparvion]

The issues was resolved by upgrading Allure from v2.9.4 to v2.11.2.