Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 24.9.0 #3271

Closed
14 of 15 tasks
joshuarli opened this issue Aug 15, 2024 · 3 comments · Fixed by getsentry/sentry#77676
Closed
14 of 15 tasks

Release 24.9.0 #3271

joshuarli opened this issue Aug 15, 2024 · 3 comments · Fixed by getsentry/sentry#77676

Comments

@joshuarli
Copy link
Member

joshuarli commented Aug 15, 2024

previous 24.8.0 | 24.9.0 | next 24.10.0

@joshuarli joshuarli changed the title Release 24.8.0 Release 24.9.0 Aug 15, 2024
@joshuarli joshuarli mentioned this issue Aug 15, 2024
9 tasks
@aldy505
Copy link
Collaborator

aldy505 commented Aug 28, 2024

Don't forget to remind people on the Github release note to upgrade to 24.8.0 before going for 24.9.0, since 24.8.0 is a hard-stop getsentry/sentry-docs#11146

@hubertdeng123 hubertdeng123 pinned this issue Sep 11, 2024
@hubertdeng123 hubertdeng123 mentioned this issue Sep 16, 2024
15 tasks
@theneva
Copy link

theneva commented Sep 17, 2024

I'm curious about the Release self-hosted list in the issue. The tag was released 11 hours ago, and the first task (pointing to getsentry/publish#4327) is checked off – but the third task (Accept (publish) the release) is still unchecked, and the issue is still open.

What's the difference between those two tasks – and when should I consider it "safe" to upgrade?

(Sorry to any subscribers to this issue who don't care about this; I couldn't find a better place to ask.)

@hubertdeng123
Copy link
Member

It is safe to upgrade here. The release of self-hosted has already gone out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Archived in project
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants