How does Sentry's semantic versioning work?

Question

I’ve just done a new release to our customer and manually uploaded the version with:

sentry-cli releases new -p myproject 0.0.53
sentry-cli releases --org mycompany deploys 0.0.53 new -e beta

0.0.53 shows up in the Releases list. It’s top of the list of releases sorted by Semantic Versioning. But the list sorted by Build Number shows “There are no releases with semantic versioning”: https://sentry.io/organizations/mycompany/releases/?sort=build

If “0.0.53” isn’t semantic versioning then what is?

Update:

I'm confused because although in Bind The Version they give the example [email protected]+1234 elsewhere they mention using semver 2.0.0 - this accepts a version MAJOR.MINOR.BUILD with no brackets. Also in Passing Additional Data the version is shown as "2.3.12" which is the same format as what we're providing now.

Answer 1

From their documentation on release, it looks like they are expecting a value comprised of package name, version number, and build number, like so -

[email protected]+1234

More details here - https://docs.sentry.io/platforms/javascript/configuration/releases/#bind-the-version