Hey team, I would like to suggest a new section called Migrations on GrowthBook documentation. Background: Our team subscribed to GrowthBook Pro plans for over a year, and since then GrowthBook SDK has been improved a lot. Recently, I decided to drive SDK migrations from 0.27.0 to 1.1.0 but it's not clear to everyone which part of the code should be changed and no suggestions or notices have been provided.🥲 Example: I think this one could be a good example 👉 https://express-validator.github.io/docs/migration-v5-to-v6

Thanks for the feedback @sparse-guitar-91772! Which SDKs were you using particular?

Hi @strong-mouse-55694 We mainly use JS SDK:

0.27.0

, which was published 1 year ago😂

We have a changelog of updates to the JS SDK. Looking through it, I don't see any explicit breaking changes. Have you experienced problems when migrating?

Oh, we haven’t started migration yet. We probably have about 10 projects that integrate with GrowthBook, including web, node and mobile. Stability and security are the most important things that we value. It would be better if GrowthBook provides migration guidelines so our team could quickly check and update. If not, I will look through the changelogs and create guidelines internally, not a big problem so far as you said “no explicit breaking changes”.

Looked back at the change notes. There are lots of new features but again nothing that seems like it will be a breaking change. However, here are some changes to be aware of: ​*­ (v1.0.0 - May 1, 2024)*​: - ​`loadFeatures`​ is replaced by ​`init`​ and ​`initSync`​. - Changes in behavior of ​`enableDevMode`​ option (no longer disables cache by default; must specify ​`disableCache: true`​). - Network requests no longer start automatically when creating a GrowthBook instance. They wait for ​`loadFeatures`​ or ​`init`​. ​*(v0.32.0 - Jan 11, 2024)*​: - The methods ​`setAttributes`​, ​`setAttributeOverrides`​, ​`setForcedVariations`​, and ​`setURL`​ are now async and return a Promise. No code changes are required since these all returned ​`void`​ prior to this.

Thanks for the summary!