Skip to content

chore(deps): update dependency org.apache.maven.plugins:maven-gpg-plugin to v3.2.8 #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency org.apache.maven.plugins:maven-gpg-plugin to v3.2.8 #100

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>3.0.1</version>
<version>3.2.8</version>

@augmentcode augmentcode Bot Apr 27, 2026 •
edited
Loading

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a major version jump (3.0.1 → 3.2.8); newer maven-gpg-plugin releases introduce additional “best practices” warnings/behavior that can break non-interactive signing depending on the CI GnuPG/pinentry setup. Consider validating that the release profile still signs successfully with the current --pinentry-mode loopback configuration in your release environment.

Severity: medium

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

<executions>
<execution>
<id>sign-artifacts</id>
Expand Down
Loading