There is a script in the Packman Discord srpm package (0.0.31-1699.98.pm.1)
that is supposed to defeat the upgrade check that Discord does when they
release a new version. This pops up a box to grab a deb or a tarball to update
outside the Suse system. This script that is in the rpm spec file apparently
has not worked for a while. I don't know if it can work, but it is in there and
inoperative. The idea according to the script is to bypass the update check
lockout and give the package maintainer time to update the Discord package
without locking users out of Discord until that is done. This is a very good
idea.

In the last few Discord update cycles the box pops up and at that point you
can't start Discord until the new package is released by the package
maintainer.

I did see a while ago a forum post about bumping the JSON file revision number
by one version to get around this manually:
(/usr/lib64/discord/resources and edit the build_info.json file) 

This appears to work but it's a kludge and the script is a better and a more
appropriate way to do this if doing it is still possible.

I'm just passing along the discovery and hoping defeating the lockout is still
possible. I use Discord daily on the Suse Discord and users getting locked out
is disconcerting.

Thanks in advance.