Well shoot. I updated this component tonight to pick up the latest commit “Switch to new API to render into plugin outlet. (#37)” My one custom link disappeared, and I can’t get it to display again. I’ve uninstalled, reinstalled, restarted to no effect.
(I’m not sure why I’m on a Beta – I simply did the official Docker install.)
If I go to the Upgrade tab, I do see an upgrade available. But it’s for v3.2.0.beta1 …which sounds older than 3.2.0.beta2…? What’s the significance of “-dev”? I can’t find any docs explaining the beta release progression/situation.
In general, should a component really be able to offer an update that isn’t compatible with the installed Discord release? That seems to invite this kind of confusion. I’d have expected behavior like Wordpress plugins, which will clearly indicate that they are holding back until you update your base installation.
As you can read there, you only get notified to update when there is a new milestone. If you were told to update after every commit, that would be several times a day.
When you notice a bug it’s always good to update first to check whether it was already fixed.
Thanks for the links, @Moin – I’d checked release pages, Github, etc. but didn’t search deep enough here.
This clears up a lot of my questions in theory. But after reading…
“we’re starting the 3.2 development cycle with 3.2.0.beta1-dev . When that’s ready to be released, it will be stamped as 3.2.0.beta1 , and then we’ll followup immediately with another commit to start development of 3.2.0.beta2-dev .”
…I’m still not sure if I should “update” from beta2-dev to beta1.
I may just sit tight until a milestone notification.