I installed discord using sbopkg, and discord is nagging me to update. How do I update all the sbopkg?

Open a terminal, sign on as root, and start sbopkg.
Tell it to sync with the remote repository.
Tell it to, "List potential updates to intalled SBo packages"
You should be able to figure it out from there.

some stuff's updated, but discord still says it needs to update

Sometimes the maintainer of a slackbuild will not be up to date on the latest software. That discord update only showed up in the last week, so it may take some time for the maintainer to get around to it.

In the meanwhile you can just update it yourself by downloading the discord-0.0.13.deb source and either run the slackbuild using "VERSION=0.0.13 ./discord.Slackbuild", or, edit the "VERSION=" line in the discord.Slackbuild file and then run it. That will build a new .tgz package in /tmp, then you can use upgradepkg to update your discord install. I just did that two days ago and it worked fine here.

2 members found this post helpful.

Excellent point!
Thanks for bringing that up.
Downloaded the source and updated several SBo packages myself, as needed.

1 members found this post helpful.

I'm the maintainer for discord and didn't realize an update was available. I'll get one pushed out before the public SBo update this weekend.

1 members found this post helpful.

Within sbopkg itself, you can search for the discord package, choose Custom, choose the .info file, change all occurrences of 0.0.12 to 0.0.13, choose the SlackBuild, edit the version in there, then choose Process. It will ask if you want to use your local changes, and when you confirm, it will download the new package, error on the md5sum, and give you the chance to build anyway. That should build and install an updated package for you.

2 members found this post helpful.

Here's another way, since I update SBo packages just for myself fairly often (Zoom...). I keep a git repo (-current or stable), and generally in the directory for a given SlackBuild can just do:
Which will download, update info/SlackBuild (including md5sums), and build/install it. Actually with sbuild it can do a test run and check if the build process does any writing outside of /tmp.

There's a screencast included here that shows how it works. It's kind of aimed more at maintainers, but anyone could use it. Note that it won't work for multi-line download .info files (usually any rust build), or any SlackBuild that's more complicated than needing a $VERSION bump.

If you really need something new it is possible to download the new source and edit the slackbuild to reflect the new version. Sometimes that just works. When it doesn't you are told what's lacking and most often that's less than a handful and easily remedied. For example I jumped two versions of GIMP recently this way.