microsoft
Beachball tries bumping package to version that already exist despite no changes
Our publishing pipeline occasionally fails when beachball tries bumping a package to a version that already exists despite no changes in that package. We're not sure why this happens but it seems occur with newer packages that were recently added to the repo. In order to fix the pipeline, we've been making small changes in the package that beachball tried bumping in order to trigger a version bump in that package. This unblocks us for a bit but the issue continues to pop up.
We saw this issue and are wondering if it could be related to this problem?
Hmmm, that's an old issue (feature request, really) that actually got implemented! However, the build pipeline error looks a lot like there was already a package published with that version. Simply run beachball sync and it'll bump all the files locally to the latest versions from the npm registry. After that, you'll need to run beachball change once more (maybe picking some patch versioning to make sure beachball publish is working again). After that, do a PR to just have changefiles.
Hey @kenotron , we're still running into this issue and seem to run into it every time we make a new package. I ran beachball sync / change which seems to do nothing (implying we are in sync).
The latest round of failures is this:
ERROR: Attempting to bump to a version that already exists in the registry: @fluentui-react-native/[email protected]
v 0.0.9 is what exists locally and in NPM. When I tried running beachball publish locally, I noticed something interesting in the CHANGELOG.json of @fluentui-react-native/badge. Line 9 says "undefined" which seems like a bug? Also worth noting that the comments are a duplicate of the earlier ones. Nothing about the change files in the repo at the moment suggest to me we need to bump @fluentui-react-native/badge...
Logs: https://dev.azure.com/ms/ui-fabric-react-native/_build/results?buildId=268300&view=logs&j=745f91f2-6a7c-581b-9fbc-0f5efa6695e3&t=057fded1-6a1e-5930-41c9-5e031da69958
@kenotron This issue is blocking us from publishing every few days. We don't want to keep having to work around it by creating an none changefile for the package every time to get it unblocked, especially since the same package is causing us issues. We have also tried bumping the version using a patch changefile. Could we get some guidance on how to fix this?
