This is the introduction of Mini-program gray release.
Everytime before you golive the mini program version, you have to choose a release strategy. If it's the first version, you have to choose it full release.
- Full Release
- Scale Release
- Whitelist Relase
Full release means it will release the version directly.
Scale Release means only a part of users can access to this version, the others will access it's last version. For exmaple: if developers set scale release 10, that means only 10% users will access this version base on same sdk compability.
|1.2.2||^2.0.0||2020/10/22||Gray release (10%)|
|NV||Binded SV||Loaded MV|
|2.36.1||1.3.0/2.1.0||90% -> |
|2.36.2||2.1.0||90% -> |
Whitelist release is used for providing access to specific users. Developers can add user's device id into the list and then thoes users are able to access this version.
Whitelist -> Gray release -> Full Release
When an audit version is approved, developers have to set it gary release.
After set it gray release strategy, it's allowed to go live this version. Once it's released, developer can adjust the release strategy as well.
- Release status can't be from Gray Release to whitelist release.
- If there is a gray release, we will block the rollback and publish a new version behavior
- If developers find some issues on gray release version and want to remove it, this gray release verison can be deprecated.
- Can I have multiple gray release version at the same time ?
No, it only support one version on gray release status(scale release and whitelist release).