The python SDK uses git rev-parse --short HEAD to determine a release from a git repository. sentry-cli releases propose-version returns the full-length hash for HEAD.
If I were to use sentry-cli's proposed version to make a release when deploying, and let sentry-python automatically detect the release at runtime, would they be both referring to the same release? On the one hand, the hash are not exactly equal, so they could be considered different, but on the other hand, they semantically are "the same" according to git.
One way to find out would be to actually try it, but I still haven't configured releases on my project and thought I might try to see if that would be a viable option before going too deep into it 😃
The python SDK uses
git rev-parse --short HEADto determine a release from a git repository.sentry-cli releases propose-versionreturns the full-length hash forHEAD.If I were to use
sentry-cli's proposed version to make a release when deploying, and letsentry-pythonautomatically detect the release at runtime, would they be both referring to the same release? On the one hand, the hash are not exactly equal, so they could be considered different, but on the other hand, they semantically are "the same" according togit.One way to find out would be to actually try it, but I still haven't configured releases on my project and thought I might try to see if that would be a viable option before going too deep into it 😃