Kamil Ogórek
Kamil Ogórek
Closes https://github.com/getsentry/raven-go/pull/227 Closes https://github.com/getsentry/raven-go/pull/137 Fixes https://github.com/getsentry/raven-go/pull/228
ref: https://github.com/alecthomas/gometalinter
I couldn't find any reliable way to extract current package name, as in here: https://github.com/getsentry/raven-go/blob/238ebd86338d2e91cb5c84663d695877dd5d0ff4/stacktrace_test.go#L109-L135 due to Go Modules not using GOPATH anymore. Need more investigation. Some sources: https://github.com/golang/go/wiki/Modules#migrating-to-modules https://research.swtch.com/vgo-module
The cumulated issue for: https://github.com/getsentry/raven-go/issues/79 https://github.com/getsentry/raven-go/issues/83 https://github.com/getsentry/raven-go/issues/179 https://github.com/getsentry/raven-go/issues/198
There's no way to do this right now. Ref: https://github.com/getsentry/raven-go/issues/125#issuecomment-436206746
Currently, when we release a preview version (beta, alpha, or RC), it publishes it with `next` tag on the NPM registry: https://github.com/getsentry/craft/blob/master/src/targets/npm.ts#L181-L189 However, when after a few iterations we perform...
1. Our Brew releasing workflow doesn't understand to not publish itself when a newer major is present, and it overrides it, which makes patches for older versions override the latest...
When publish action fails, either due to an error, or a timeout, a pre-created draft release will be left untouched. This means, that whenever someone reapproves the release, they can...
We do already have our own logic implemented here - https://github.com/getsentry/craft/blob/2d8ba63ab9670d9b20c8c9e1a082ab60175c2594/src/targets/github.ts#L297-L333
Once implemented, test it out on sentry-cli. ref: https://github.com/getsentry/sentry-cli/issues/433