Good questions, thank you for asking.
(1) The reason this was released as an update rather than a new Plugin was because we weren’t changing or even updating any functionality, just updating the underlying library to address a handful of reported bugs with the existing Plugin. If we had simply deprecated the existing plugin, we would be essentially forcing existing users to migrate to a new plugin just to have their bug fixed.
(2) We reserve Bubble Versions for breaking changes only - that is, an update to the platform that knowingly breaks an existing way of doing something (though, for good reason ). This update did not meet that criteria. Unfortunately, there was a breaking bug reported after the update, but this was due to legacy app language settings not playing nice with the new library and was quickly resolved by gracefully handling the legacy app language. Breaking changes usually require intervention from the user to update their settings, workflows, UIs, etc.
This does bring up a good point about versions for hardcoded Bubble-built plugins though, and I’m totally on-board. Rest assured it is something we are looking into so that you all will have more control over when you receive any Plugin updates.