Skip to main content

Why are my releases not marked as semver (semantic versioning)?

Updated over a month ago

Issue

I am creating releases using semver, for example 1.2.3+45, but Sentry is marking them as not semver.

Applies To

  • All Sentry users

Resolution

Sentry only identifies releases as semver when the release name follows the format package@version or package@version+build.

Adjust your release creation scripts and/or the release option in your SDK initialisation to match the format above.

Did this answer your question?