You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the 2.0.0-rc.1 release, the meta.SDKVersion got set to "2.0.0-rc.1" and the meta.SDKPrerelease got set to "". This is due to a faulty regexp in our release scripts.
Fortunately, this should only impact users that are referencing meta.SDKVersion and meta.SDKPrerelease directly. Users using meta.SDKVersionString() will receive the correct result; it's just not split into its constituent variables correctly.
We should resolve this for 2.0.0-rc.2, but because the impact is fairly minimal for the moment--most users probably won't notice--it probably doesn't justify an emergency release.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Jun 12, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For the 2.0.0-rc.1 release, the
meta.SDKVersion
got set to"2.0.0-rc.1"
and themeta.SDKPrerelease
got set to""
. This is due to a faulty regexp in our release scripts.Fortunately, this should only impact users that are referencing
meta.SDKVersion
andmeta.SDKPrerelease
directly. Users usingmeta.SDKVersionString()
will receive the correct result; it's just not split into its constituent variables correctly.We should resolve this for 2.0.0-rc.2, but because the impact is fairly minimal for the moment--most users probably won't notice--it probably doesn't justify an emergency release.
The text was updated successfully, but these errors were encountered: