Skip to content

AP-757: Update to Rails 8.1, Ruby 3.4, and other dependencies#42

Open
anarchivist wants to merge 1 commit into
mainfrom
AP-757
Open

AP-757: Update to Rails 8.1, Ruby 3.4, and other dependencies#42
anarchivist wants to merge 1 commit into
mainfrom
AP-757

Conversation

@anarchivist

Copy link
Copy Markdown
Member

No description provided.

@awilfox awilfox left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r+wc - Looks good to me, but we can move Puma further if we know Rack 3 is okay.

Comment thread Gemfile
gem 'omniauth-cas', '~> 3.0'
gem 'omniauth-rails_csrf_protection', '~> 1.0'
gem 'puma', '~> 5.6', '>= 5.6.8'
gem 'puma', '~> 6.0'

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're going to Rack 3 (which I still am not 100% sure is safe since it rewrites headers), we can go all the way to Puma 8 with no issues. The only blocker was Rack 2.x.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we're unable to move to Puma 8 because of puma-plugin-delayed_stop, and I'm not sure how big of a lift is there. cc @danschmidt5189

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the very least, Framework and LAF are both on Puma 7.2, so I know that's safe to use. And I believe there's a single CVE (low priority) on Puma 6 that is a WONTFIX (but is fixed in 7).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants