Your latest APK is signed by a different key than the releases before, and I could find no hint on that in the release notes. Thus it is incompatible to the previous ones, which cannot be updated with that APK. It also means the update was rejected by my repo, so it won't even be offered to people for first-time installation.
Can you please explain the reason, so we can see what possible ways forward exist?
Signer #1 certificate DN: CN=Atticus Cornett, O=Atmos Weather, L=St. Clair County, ST=Alabama, C=AL
Signer #1 certificate SHA-256 digest: 3008ee877a1ffa5a456cc953fee1dc14dad2769c1510815ebbd2b2330b6c1a6a
Signer #1 certificate SHA-1 digest: d087521aa67e34cc8b791e21792bafb2cbd7c178
Signer #1 certificate MD5 digest: a34735bc8d4e6be3d51e4e0877c58438
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 certificate DN: CN=Atticus Cornett, O=Atmos Weather, L=St. Clair County, ST=Alabama, C=AL
Signer #1 certificate SHA-256 digest: c9c9bffa8ff1be993e7af9326b24fc99344298a25ee086e8e4f00b90a015a73f
Signer #1 certificate SHA-1 digest: b04b50015239f3455a5f32027153bd9fd6291d7a
Signer #1 certificate MD5 digest: 3a5e1f4b8262b87a2f9c43b2fc37318d
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048