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
The react-native-windows mono repo uses beachball and publishes nightly prerelease builds out of main to our canary tag (i.e. with versions react-native-windows@0.0.0-canary.XYZ).
Dependabot bumped our beachball from 2.43.0 to 2.43.1, and now beachball has published the very odd react-native-windows@0.0.1-0. I see no explanation for this on our end as our change files are still type: prerelease, dependentChangeType: patch.
The react-native-windows mono repo uses beachball and publishes nightly prerelease builds out of main to our canary tag (i.e. with versions
react-native-windows@0.0.0-canary.XYZ
).Dependabot bumped our beachball from 2.43.0 to 2.43.1, and now beachball has published the very odd
react-native-windows@0.0.1-0
. I see no explanation for this on our end as our change files are stilltype: prerelease
,dependentChangeType: patch
.Beachball's publish commit (using 2.43.1): microsoft/react-native-windows@0784c77
Beachball's previous publish commit (using 2.43.0): microsoft/react-native-windows@2731008
The text was updated successfully, but these errors were encountered: