Suppose I have multiple developers working on a shared library published by KMMBridge. Each developer is working within their own branch. What's the best way to differentiate releases from those builds to avoid version conflicts (i.e. two developers try to publish a version 1.0.1)

Are you publishing in-progress builds from each developer's branch, or final builds when they merge? Is each developer publishing manually or is it happening in CI?

Publishing in-progress builds. For example, we have a feature branch in our iOS+Android and want to test a corresponding change in the shared library before publishing a new "official" version. Currently we are just appending a Jira tag to our

LIBRARY_VERSION

for example:

LIBRARY_VERSION=1.0.0-JIRA-1234

Wasn't sure if there was a better way.

Assuming you're testing yourself as you build, our usual workflow would be to use a local development flow (docs for cocoapods or spm). If you want to pass a build to other devs to test, then we don't really ship anything for that, but appending a tag like you're doing probably makes sense. One caveat is, if your consuming app is not set to use an exact version number, you might pick up one of those dev versions by mistake.