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.

Sign up for GitHub

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

Jump to bottom

Missing release on rubygems.org? #2221

Closed
gael-ian opened this issue Jan 9, 2024 · 4 comments · Fixed by #2222
Closed

Missing release on rubygems.org? #2221

gael-ian opened this issue Jan 9, 2024 · 4 comments · Fixed by #2222
Assignees
@sl0thentr0py
Labels
question Type: Bug

Comments

@gael-ian
Copy link

gael-ian commented Jan 9, 2024

Hello,

All sentry gems for Ruby seem to have been updated to 5.16.0 but sentry-rails and sentry-delayed_job are still only available as 5.15.2 on rubygems.org. Maybe there was a bug with the release script? Can you push them manually?

Thanks.
@ryanb-gds ryanb-gds mentioned this issue Jan 9, 2024
Merged
@floehopper floehopper mentioned this issue Jan 9, 2024
Merged
@sl0thentr0py
Copy link
Member

oh damn, on it

@sl0thentr0py
Copy link
Member

sigh, github is also having an incident right now, I'll try to get it out as soon as they're back up.

@sl0thentr0py
Copy link
Member

cause was failure to install latest sqlite3 release

sqlite3-1.7.0-x86_64-darwin requires ruby version < 3.4.dev, >= 3.0, which is incompatible with the current version, ruby 2.7.8p225

@sl0thentr0py sl0thentr0py mentioned this issue Jan 9, 2024
Merged
@sl0thentr0py
Copy link
Member

@gael-ian 5.16.1 was released correctly for all gems, sorry for the inconvenience!

@sl0thentr0py sl0thentr0py mentioned this issue Jan 9, 2024
Merged
jkempster34 added a commit to alphagov/whitehall that referenced this issue Jan 10, 2024
@jkempster34
Update sentry-rails to 5.16.1
dfee89a 
A bad release of sentry-sidekiq yesterday
(getsentry/sentry-ruby#2221) caused sentry-rails to
be downgraded to 5.3.1 rather than updated.

As a result, we are seeing some odd behaviour where instead of being shown
error pages specific to the error, we are always shown the production server
error page. This is present in production, but also extends to the development
environment where we no longer see the developer exception pages.

This brings sentry-rails in line with sentry-ruby and fixes the issue.
@jkempster34 jkempster34 mentioned this issue Jan 10, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sl0thentr0py sl0thentr0py

Labels
question Type: Bug
Projects
GitHub Issues with 👀 2
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Pin sqlite3 for building gems getsentry/sentry-ruby
2 participants
@gael-ian @sl0thentr0py