Post

Dear gem maintainers 👋 Rails 8.1 just dropped, but many gems can’t be used because of overly strict gemspec constraints. Please don’t hard-restrict Rails versions, let us test early and report real issues sooner! ❤️ Thanks

Hans Lemuet 🇺🇦🇵🇸

@spone.net

9 Nov 2025

Would you recommend just dropping the `"< 8.1"` part in your screenshot?

Adrien Poly

@adrienpoly.com

10 Nov 2025

yes. I have opened several issues to gem with a link to @byroot.bsky.social comment here github.com/svenfuchs/ra... for those gems every last major Rails release was just updating that line. I think having in the readme and in the CI matrix the official supported version is good enough.

github.comUpdate for Rails 8 by Schwad · Pull Request #1130 · svenfuchs/rails-i18nRef: #962 Allow runtime railties 8.0.0 dependency. Bump version number to 8.0.0. Update Gemfile.lock.

Hans Lemuet 🇺🇦🇵🇸

@spone.net

10 Nov 2025

Thanks for the link! I'll bring it up for ViewComponent!

Adrien Poly

@adrienpoly.com

VC only Rails dependency is ActiveSupport. I am pretty sure that if there is a breaking change in ActiveSupport it would be picked up by a CI running against Rails main.

10/11/25, 1:54 pm0 reposts1 like

Hans Lemuet 🇺🇦🇵🇸

@spone.net

11 Nov 2025

I opened github.com/ViewComponen... and github.com/pantographe/... ;)

github.comRemove Rails dependencies upper bound by Spone · Pull Request #2497 · ViewComponent/view_componentWhat are you trying to accomplish? To avoid having to push the upper bound on every Rails major release, let's remove it altogether. Our CI suite already tests ViewComponent against Rails main....