-
-
Notifications
You must be signed in to change notification settings - Fork 220
Set release to -dev
after publishing
#2160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The recent (.NET 8) default addition of the commit hash as part of AssemblyInformationalVersion might help address this, maybe the sentry SDK could recreate this format for older .NET SDKs/Framework |
@jamescrosswell with #3462 merged, we're going to run into this issue, right? |
Very likely yes. At least now with SetCommits we should get specific commits associated with each release as well but it would still be misleading to associate all our dev work on release N + 1 with release N... so I think Matt's suggestion of adding some suffix like |
With
sentry-cli
, we don't want to accidentally associate release info for work-in-progress with the last shipped release. Currently, that would happen because we keep the<Version>
inDirectory.Build.props
untouched until publishing each release.Add a small post-release script to add a
-dev
tag.The text was updated successfully, but these errors were encountered: