Closed mikesun closed 2 years ago
I don't know what the accepted practice is. Do you have a better suggestion?
Hello @knz, I was checking the dependencies in one of the projects I work on, spotted the old sentry-go version and ended up here.
Seeing this diff my best guess is that on some occasions, it has been useful to jump ahead and pin the dependencies at on a specific commit on the master
branch.
Would you want something done about it?
errors
to use directly getsentry/sentry-go
Reading through their changelog, there are no mentions of any breaking changes.
This package uses its own fork of sentry-go which means a user of this package has to use the forked version when initializing the sentry client. Is that the accepted practice around this?