Never let an expired signing key block a release
On the first Monday of every month, WebRun opens Sonatype's Maven Central publishing portal, checks the GPG signing key's expiry date, books a calendar reminder well ahead of the expiry so there's time to generate and distribute a new key, and posts a heads up to Microsoft Teams so a release never gets blocked by an expired signing key nobody noticed.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I avoid an expired Maven Central signing key blocking a release?
WebRun checks the Maven Central signing key's expiry date on the first Monday of every month. It books a calendar reminder and posts a Microsoft Teams heads up whenever fewer than 60 days remain, so there's always enough runway to generate and distribute a new key before an expired one blocks a release.
- Signing key renewal gets 60 days of runway instead of a last minute scramble
- Releases never get blocked by a key nobody noticed had expired
- The team gets one clear heads up instead of discovering it during a publish
Built for Java engineering teams · open source maintainers · release managers · platform teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
central.sonatype.comin a real browser with your saved login - no setup, no API keys. -
1
Sonatype Maven Central - check the signing key's expiry date
sonatype.com
WebRun opens Sonatype Maven Central to check the signing key's expiry date. - Open the Maven Central publishing portal and check the signing key's current expiry date
- Calculate how many days remain until it expires
- Flag it when fewer than 60 days remain
Done when The signing key's expiry date and days remaining are captured.
-
2
Google Calendar - book a renewal reminder
calendar.google.com How to Automate Google Calendar
WebRun opens Google Calendar to book a renewal reminder. - Book a renewal reminder well ahead of the expiry date when fewer than 60 days remain
- Add the exact expiry date to the reminder
- Skip creating a duplicate reminder if one already exists
Done when A renewal reminder is booked whenever the key has fewer than 60 days left.
-
3
Microsoft Teams - post a heads up to the team
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to post a heads up to the team. - Post a heads up to the release channel when the key is within 60 days of expiry
- Name the exact expiry date
- Skip the post when the key has plenty of runway left
Done when The release channel has a heads up whenever the key is within 60 days of expiry.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it renew or regenerate the signing key itself?
No. WebRun only reports the expiry date. Generating and distributing a new signing key is always a deliberate action your team takes.
Why 60 days of warning?
Because generating a new key and getting it trusted and distributed takes real time, so 60 days leaves enough runway to do it without rushing before a release.
What happens once the key is renewed?
The next check finds a fresh expiry date well beyond 60 days out, so the reminders stop until it's due again.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.