Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Upgrade Rails 8.0 -> 8.1

未关闭
#888 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
rails, ruby
领域
backend, devops

调研方向

从被阻塞的 issue #887 开始,然后检查 Rails 版本约束并运行 bin/rails app:update。检查 8.1 的框架默认值及其对序列化格式的影响;完成的标准是完整测试套件通过,并且 staging 已在 production 之前完成 soak。

由索引模型根据 Issue 内容生成。

描述

type:infrastructure

Why

Final step. Verified that rails 8.1.3.1 resolves cleanly against this gem set today.

Scope

  • gem "rails", "~> 8.1.0", bin/rails app:update
  • Framework defaults for 8.1 handled the same way as the previous two: commented first, flipped in a separate deploy if any affect serialization formats

Acceptance criteria

  • Full suite green
  • Staging soak before production

Blocked by

#887 (Rails 8.0 defaults).


Known remaining work after this sequence

  • OmniAuth 1.9 -> 2.x / Rack 2 -> 3. Rails 8.1 resolves fine while staying on Rack 2.2.24, because omniauth 1.9.2 caps rack < 3 and actionpack 8.1 only needs rack >= 2.2.4. So this does not block the upgrade — but it leaves the app on omniauth 1.x, which carries CVE-2015-9284 (authentication request forgery). Fixing it changes the auth request from GET to POST with a CSRF token, which breaks both the Ember and native clients until they are updated. Deserves its own issue and its own schedule.
  • AMS 0.9.8 -> 0.10.x, or off AMS entirely. The pin is a deliberate freeze, not a fix.
  • PostgreSQL 12.8 and MongoDB 4.4.9 are both past end of life in docker-compose.yml and CI.

Part of the Ruby + Rails upgrade sequence. Ruby 3.2 reached end of life on 2026-04-01 and the backend is on Rails 7.1; the goal is Ruby 3.4.10 and Rails 8.1, in steps that each keep CI green and are independently deployable.

主要语言
Ruby
星标
50
派生
21
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

rubyforgood/Flaredown 的其他 Issue

查看 rubyforgood/Flaredown 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。