Burak Yigit Kaya
Burak Yigit Kaya
Okay so identified the issue here. It is just a merge error, nothing to do with Craft itself. This happens in https://github.com/getsentry/sentry-react-native/commit/56c9319624c38be2331113ff17e2ac48db628098. The actual Changelog and the changelog entry in...
@marandaneto @bruno-garcia >The problem with auto is that every merged PR is gonna be within the release, even meta changes or non user-facing changes. >We try to keep our changelog...
>I've fixed them manually, they were wrong and that's the reason I've opened this issue. >Changelog file and Github release page both included a wrong PR within the published version....
Hi @George3d6 and thanks for reporting this issue! Happy to come by a passionate `sentry-cli` `bash` folk like myself as I want to use this feature over at getsentry/onpremise#740 but...
Ping @kamilogorek @jan-auer
Ping @bestander @arcanis @Daniel15 @kittens
May be we can add a sentence about why signing is important?
Agree with "too much purple/too dark" complaints. Rest looks pretty good. Key points got my attention immediately that we want a user looks answers to: - What is this thing?...
Is this still an issue? Can someone try with a recent version of Yarn?
Related: #1705. I think instead of introducing a postgres version variable, it would be better to introduce a [hard-stop](https://develop.sentry.dev/self-hosted/releases/#hard-stops) upgrade point, add the script there, and then remove it afterwards.