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

Upgrade Rails 7.1 -> 7.2

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

还没有人认领这个 Issue。

评估

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

调研方向

首先检查 Rails 依赖范围以及两个阻塞 issue:#881 和 #882。运行 bin/rails app:update,将 config.load_defaults 保持为 7.1,保留生成的 7.2 默认值注释,并移除 config/initializers/new_framework_defaults_7_1.rb。完整测试套件在 deprecations raising 的情况下通过,并且 staging 完成 soak,即视为完成。

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

描述

type:infrastructure

Why

First framework step. With the prep and the two blocker gems done, this should be close to mechanical. Verified to resolve cleanly.

Scope

  • gem "rails", "~> 7.2.0"
  • Keep config.load_defaults at 7.1. Run bin/rails app:update, take the generated new_framework_defaults_7_2.rb with every option still commented. Enabling them is a separate issue — upgrading the framework and changing its behaviour are two different changes, and some defaults alter serialization formats that must not flip in the same deploy.
  • config/initializers/new_framework_defaults_7_1.rb can be retired: it is already fully worked through and load_defaults 7.1 is set, so it is bookkeeping.
  • Rails.application.secrets is removed in 7.2 — already handled by the prep issue.

Note Rails 7.2 requires Ruby >= 3.1, so this lands fine on the current Ruby 3.2.3.

Acceptance criteria

  • Full suite green with deprecations raising
  • load_defaults still 7.1
  • Staging soak before the defaults are flipped

Blocked by

#881 (Mongoid 9) and #882 (Globalize 7) — both hard resolution blockers. Blocks #884 and #885.


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 摘要。