Skip to content

[deploy] Release attempted despite expired singing key #1930

@scordio

Description

@scordio

Expected Behaviour

If I understand #1740 correctly, releases should fail when the signing key has expired.

Actual Behaviour

I've recently attempted a release and the signing key expiration was detected:

[WARNING]     [mavenCentral] Signing key 1FF7DB4EE9370644 expired at 2025-06-23T16:36:56

However, the release wasn't stopped and seemed to have completed successfully:

[INFO] JReleaser succeeded after 08:56 m

And Maven Central seems happy too 🤔

Am I missing something?

Environment Information

  • Operating System: Ubuntu (GitHub Actions)
  • JReleaser Version: 1.19.0
  • JDK Version: 21

Here is the JReleaser Maven plugin configuration and release logs.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workinggood first issueGood for newcomersreleasedIssue has been released

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions