Andres Almiray

Oh no, I explained myself badly. The idea has been discussed somewhere else and we were missing a ticket to track it. Thank you for opening a ticket for it...

Only a few package types are supported at the moment: npm, maven, rubygems, docker, nuget, container https://docs.github.com/en/packages/working-with-a-github-packages-registry

Were you able to capture the `trace.log`?

The value is set as a name template here https://github.com/jreleaser/jreleaser/blob/b658a47605e3703e313b35d5c0f5e26f90f14aae/core/jreleaser-tools/src/main/java/org/jreleaser/packagers/BrewPackagerProcessor.java#L196-L200 The version value is taken from here https://github.com/jreleaser/jreleaser/blob/b658a47605e3703e313b35d5c0f5e26f90f14aae/core/jreleaser-model/src/main/java/org/jreleaser/model/Distribution.java#L114 Whose value is set during validation https://github.com/jreleaser/jreleaser/blob/b658a47605e3703e313b35d5c0f5e26f90f14aae/core/jreleaser-model/src/main/java/org/jreleaser/model/validation/DistributionsValidator.java#L223-L225 Which is fed automatically by...

I'm afraid it does not matter when the JReleaser tasks are invoked but when the JReleaser plugin is applied as the project configurer is called right away and by that...

FWIW defining a `targetCompatibility` property in `gradle.properties` should be enough regardless of the JDK used to run the build, for example **gradle.properties** ``` targetCompatibility = 11 ``` Supposedly the `java-base`...

And then I get to eat my own words because we already make use of `afterEvaluate` to configure the model https://github.com/jreleaser/jreleaser/blob/b658a47605e3703e313b35d5c0f5e26f90f14aae/plugins/jreleaser-gradle-plugin/src/main/groovy/org/jreleaser/gradle/plugin/JReleaserPlugin.groovy#L53-L65 Somehow I still think this is a timing issue....

Configuration cache is an incubating feature yet it fails the build when enabled and if it encounters issues ... will have to keep an eye on it.

Thanks. I used to be a big Gradle proponent for years but the churn of updating idioms and breaking changes between 5 and 7 got me down for the time...

Bitbucket does not host files/releases by itself like other options do (GitHub/GitLab/Gitea). Supporting Bitbucket will require interacting with additional APIs to create a release and upload files.