I just received an email from account@notification.bubble.io asking me to confirm if I’m updating my plugins, otherwise they will grant editor privileges to another author to help upgrade.
Interested in who exactly would be upgrading your plugin if you didn’t respond, hopefully it would be someone from Bubble w/ notes in the changelog or something.
the funny thing is that the same email is sent also to private plugins (and to the wrong accounts), threatening to let somebody else fork the plugin.
Of course a private plugin is not licensed to allow forking, so that would be a copyright violation.
It would be nice to have some clarification about this. Under no circumstances bubble is allowed to violate the copyright of my private plugin.
Also still wondering about the answer for my question now a month later… at least exposing the plugins so we have a game plan for plugins that aren’t being updated in ~2-3 months??
Maybe the idea is Bubble is behind the scenes trying to get everything updated without scaring ppl, but user would still need to be aware of it so they can update and test afterwards…
I think they’re going to let users know! I received an email about it. Updated a few plugins and the changes are relatively straightforward so hopefully won’t be a huge lift!
Is that still true even with node 18 upgrade? I know this is an example update in the upgrading docs, doesn’t seem like we have to use .then .catch anymore
Oh yeah, good callout @lola—we will update these docs! Since API v4 is on node 18 and doesn’t use fibers, we now encourage plugin authors to use async/await rather than Promise.then/catch.
Honestly, the whole update process has been handled pretty poorly, without enough support or any response from bubble (including in this exact thread).
Question - as a plugin user, do I need to manually update all of my plugins? I don’t like to update plugins if everything is working the way I like as sometimes updates will break something on my end
yes, you will need to update your plugins. My suggestion is to start trying to do that now (for all plugins you are using that have already upgraded to API v4) so that you don’t have to upgrade them all at one time.
@ramzizi Yes the dev needs to update the plugin to API V4 IF there are server side actions. Then once they push the update you go into your plugin page, update it then confirm everything is still working (or fix things), then push your app to live and you are in the clear.
Not every plugin is server side actions though. If there’s specific ones you are most worried about it might be easy to tell based on what the plugin does/how it behaves or inspecting it if it’s a free plugin.
But every plugin won’t need to be on version 4 it will only break on version 3 if it’s using server-side actions. You can see the action type by going to actions and then the action type
Does Bubble notify or remind users when a plugin they’re using is available for an update to v4, especially if they haven’t updated it yet?
As a plugin author without access to directly email users, I’m concerned that some apps might face issues if they don’t upgrade to the latest version in time. Any insights on this would be appreciated.