Andres Almiray

> IMHO it is safer to add a requires static for all dependencies used in the code, both direct and transitive. It is quite common to find "undeclared" direct dependencies...

It may be the case that the shadow plugin overlooks the forced dependencies and resolves a copy of the original configuration that contains the conflicting JNA version.

You'll have to use Gradle's native way to force dependencies, or declare alternatives. I can only recommend looking at the docs https://docs.gradle.org/current/userguide/dependency_management.html

As far as I can tell this only occurs while a commit is performed on the same branch during a release. A fix will be posted in a future release....

@wendigo I see. Your case is different though the observable result is the same. What I understand from your flow is that the tag is created during the `prepare release`...

@wendigo could you post a link to a gist with your trace.log? Also, I'll update the logs to include the tagged sha. For now it looks like this ``` [DEBUG]...

Yes, this should be enough

Staged artifacts are independent from the release as they are placed in a staged directory by the build. Can you describe what happened?

@wendigo from the log you linked I can see the following: ``` > Display git status and history, checkout release tag" Run git status On branch master Your branch is...

`trace.log` reveals ``` [INFO] Project version set to 191 [INFO] Release is not snapshot [INFO] Timestamp is 2024-10-23T13:34:10.165507195Z [INFO] HEAD is at 206692e ``` I believe the problem may be...