Chad Whitacre
Chad Whitacre
Sounds good to me. Issue scope expanded! :-)
Bumping to core UI team as this seems unlikely to be specific to self-hosted.
Hrm, yeah it [looks](https://github.com/getsentry/sentry/commit/955ec49aba27d54af32bd2d630b388c2715f6ee6) like #35554 should be in 22.6.0. 🤔 @larsnystrom Are you suuuuuure you are seeing this with 22.6.0? 🧐
Interesting. Good info, thanks @larsnystrom. Thoughts @jennmueng? 🤔
Could be a product issue vs. self-hosted-specific?
> the underlying logic is spread through the whole project Can you unpack this for me @kubijo? My instinct is to route this over to the `sentry-javascript` repo as it...
Okay yeah I'm gonna bump this to the JavaScript SDK team to digest that. 😂 Thanks for the great info!
> We have some ideas FTR: https://mail.python.org/pipermail/cryptography-dev/2015-January/000371.html
In the second case when there is no old version we should build the changelog from the beginning of the repo.
It seems like GitHub could/should provide this, but [they don't](https://github.community/t/release-checksums-on-github/137764). This might actually be better in Craft since the work here would be to add checksum info to the release...