-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Release 22.4.0 #1421
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
Comments
relay snuba sentry accepted |
expecting self-hosted and sentry-docs to kick off in ~10 minutes |
relay ongoing, no visibility |
Issue with Relay: getsentry/publish#1010 (comment) Reminiscent of #1193 (comment) 🤔 |
self-hosted and sentry-docs are prepped, holding off on accepting until relay is done |
Alright what's going on, second relay run is dead in the water after an hour, still at 5 uploads. |
relay done, down in the muck on self-hosted |
Kind of a mess. The My thought was to start debugging locally to see if I could find a quick fix for the CI failure ... but I have a new M1 laptop and Best bet at this point still seems to be to fix the Could also disable docker-compose v1 checks in CI, i.e., drop Docker Compse v1 support for |
So then the question is can I fix the |
I went down the rabbit hole on #1415, afaict the CI failures in My plan is to temporarily(?) turn off the Docker Compose v1 CI checks, and restart the |
I added a note about Docker Compose v1 to the release notes. Case closed. |
22.3.0 | 22.4.0 | 22.5.0
relay
snuba
sentry
sentry-docs
self-hosted
The text was updated successfully, but these errors were encountered: