jreleaser/jreleaser

AI Summary: The `jreleaserFullRelease` Gradle task fails when using JReleaser version 1.21.0, preventing artifacts from being deployed to Maven Central. A reproducible example with a GitHub repository and steps is provided. However, the detailed error message or stacktrace explaining the cause of the failure is missing from the provided logs.

AI Summary: The `jreleaserConfig` Gradle task currently produces no output when it is executed a second time and is already up-to-date. This behavior is unexpected, as typical Gradle tasks provide an `UP-TO-DATE` message, leaving users unsure if the task ran successfully. The reporter expects some form of confirmation that the task was executed and found no changes.

AI Summary: The JReleaser `nexus3` deployer incorrectly removes the trailing slash from the configured repository URL during the `jreleaser config` step. This URL modification causes subsequent `jreleaser full-release` operations to fail with a `400 Bad Request` error, as Nexus 3 expects a specific URL format with a trailing slash for repository paths.

AI Summary: Add a default label `org.opencontainers.image.source` with the GitHub repository URL to the Docker images created by JReleaser. This will improve the metadata of the container images, making them more informative when viewed on platforms like Google Container Registry.

AI Summary: Enhance the JReleaser GitLab integration to automatically link releases with specified milestones during the release process. This involves modifying the `GitlabReleaser` to utilize the GitLab API for associating milestones with releases.

AI Summary: Investigate why a JReleaser release proceeded despite a warning about an expired signing key. This involves analyzing the JReleaser configuration, release logs, and potentially the JReleaser code itself to determine if the warning is correctly handled and if there's a bug causing the release to continue despite the expired key. The goal is to identify the root cause and propose a fix or workaround.

AI Summary: Debug a NullPointerException in the JReleaser Maven Central deployment process. The exception occurs within the `Deployable` class when `getParent()` returns null on a file path, likely due to an unexpected file structure or a bug in how JReleaser handles deployment artifacts. The task involves analyzing the stack trace, inspecting the project's build process, and potentially modifying JReleaser's logging or code to identify the root cause of the null path.

AI Summary: Improve JReleaser's error handling for Maven Central deployments. The current error message for unauthorized access ('Unexpected error') is unhelpful; it should clearly indicate the 401 Unauthorized error.

AI Summary: The issue describes a failure during Maven Central deployment using JReleaser due to a `MissingResourceException` related to XML resource loading. The task involves debugging the root cause of this exception within JReleaser's Maven deployment module, likely related to a missing or incorrectly configured XML processing dependency or resource. A solution might involve updating dependencies, adding missing resources, or correcting configuration settings within JReleaser or the project's POM files.