Andres Almiray

Hi @Shawoll, we're planning to release `1.2.0` by August 27th. If your changes are ready to merged in the coming days then please file a PR to have it included...

Just checking, do you see any emojis at all on the terminal? This is unrelated to CHANGELOG.md. What happens if you open the file with another editor? Can you see...

Also FWIW your configuration shows the use of "conventional-commits", not gitmoji. Some default values are also explicitly configured which leads to more verbose configuration.

I see. File encoding should be set to UTF_8. I wonder if JReleaser should force that encoding for you.

Good suggestion. As I understand it GitHub has a predefined set of keywords that may be used to interact with issues. I suppose GitLab and Gitea can do the same...

I see. For the time being _if_ the changelog is rendered on GitHub _and_ the content has explicit links _or_ mentions an issue by number _then_ the GitHub renderer will...

The idea is to enable OTeL to provide tracing information similarly as it's done by https://github.com/open-telemetry/opentelemetry-java-contrib/blob/main/maven-extension/README.md We may need to build this as an optional [extension](https://jreleaser.org/guide/early-access/extensions/index.html) as OTeL increases significantly...

OK, but be aware that many of the package managers supported by JReleaser expect a root entry as provided by the default behavior of the `archive` assembler. For this reason...

It's possible to implement, the underlying infrastructure already exists, but enabling the feature might leave package managers in a bind. If you use JReleaser for assemble & release? No harm...

@knutwannheden thank you for the suggestion. This particular feature has been proposed a few times but we decided to wait after `1.0.0` to tackle it. Now is a good time...