renovate[bot]
commented
2 years ago Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (v0.13.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.
This PR contains the following updates:
v0.11.0->v0.13.0Release Notes
getsentry/sentry-go
### [`v0.13.0`](https://togithub.com/getsentry/sentry-go/blob/HEAD/CHANGELOG.md#v0130) [Compare Source](https://togithub.com/getsentry/sentry-go/compare/v0.12.0...v0.13.0) - ref: Change DSN ProjectID to be a string ([#420](https://togithub.com/getsentry/sentry-go/issues/420)) - fix: When extracting PCs from stack frames, try the `PC` field ([#393](https://togithub.com/getsentry/sentry-go/issues/393)) - build: Bump gin-gonic/gin from v1.4.0 to v1.7.7 ([#412](https://togithub.com/getsentry/sentry-go/issues/412)) - build: Bump Go version in go.mod ([#410](https://togithub.com/getsentry/sentry-go/issues/410)) - ci: Bump golangci-lint version in GH workflow ([#419](https://togithub.com/getsentry/sentry-go/issues/419)) - ci: Update GraphQL config with appropriate permissions ([#417](https://togithub.com/getsentry/sentry-go/issues/417)) - ci: ci: Add craft release automation ([#422](https://togithub.com/getsentry/sentry-go/issues/422)) ### [`v0.12.0`](https://togithub.com/getsentry/sentry-go/blob/HEAD/CHANGELOG.md#v0120) [Compare Source](https://togithub.com/getsentry/sentry-go/compare/v0.11.0...v0.12.0) - feat: Automatic Release detection ([#363](https://togithub.com/getsentry/sentry-go/issues/363), [#369](https://togithub.com/getsentry/sentry-go/issues/369), [#386](https://togithub.com/getsentry/sentry-go/issues/386), [#400](https://togithub.com/getsentry/sentry-go/issues/400)) - fix: Do not change Hub.lastEventID for transactions ([#379](https://togithub.com/getsentry/sentry-go/issues/379)) - fix: Do not clear LastEventID when events are dropped ([#382](https://togithub.com/getsentry/sentry-go/issues/382)) - Updates to documentation ([#366](https://togithub.com/getsentry/sentry-go/issues/366), [#385](https://togithub.com/getsentry/sentry-go/issues/385)) *NOTE:* This version drops support for Go 1.14, however no changes have been made that would make the SDK not work with Go 1.14. The currently supported Go versions are the last 3 stable releases: 1.15, 1.16 and 1.17. There are two behavior changes related to `LastEventID`, both of which were intended to align the behavior of the Sentry Go SDK with other Sentry SDKs. The new [automatic release detection feature](https://togithub.com/getsentry/sentry-go/issues/335) makes it easier to use Sentry and separate events per release without requiring extra work from users. We intend to improve this functionality in a future release by utilizing information that will be available in runtime starting with Go 1.18. The tracking issue is [#401](https://togithub.com/getsentry/sentry-go/issues/401).Configuration
š Schedule: At any time (no schedule defined).
š¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
ā» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
š Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.