Given that your key has expired.
$ gpg --list-keys
$ gpg --edit-key KEYID
Use the expire command to set a new expire date:
gpg> expire
When prompted type 1y or however long you want the key to last for.
Select all the subkeys (the primary key, which we just set the expires date for, is key 0):
gpg> key 1
gpg> key 2
gpg> expire
A star will sppear before all selected keys.
Since the key has changed we now need to trust it, otherwise we get the error "There is no assurance this key belongs to the named user" when using they key:
gpg> trust
Test it out, do a round trip:
gpg -ea > secret.out
gpg -d secret.out
Backup the key:
gpg -a --export KEYID > kris.leech.gpg.public
gpg -a --export-secret-keys KEYID > kris.leech.gpg.private
Move the keys on to something like a USB drive and store it safely in another location.
Publish the public key:
gpg --keyserver keyserver.ubuntu.com --send-keys KEYID
gpg --keyserver pgp.mit.edu --send-keys KEYID
If you need to copy/paste the public key to a key server:
xclip -i kris.leech.gpgp.public -selection clipboard
Great! It works as expected.
Adding a few steps that need to be done after that for updating the GPG key:
Save your changes made in the GPG key
Get the content of the public key using the following command. Copy this public key.
Now, go to GitHub and delete your existing GPG key that has expired. And then click on the New GPG key button and paste the public key we have copied in step 2. Save this public key.
In this way, you have successfully updated an expired GPG key and all of the commits that are signed with the expired key are now marked from unverified to verified.