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

Enable the Rails 7.2 framework defaults

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

还没有人认领这个 Issue。

评估

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

调研方向

从 new_framework_defaults_7_2.rb 开始,将其选项与 new_framework_defaults_7_1.rb 进行比较,尤其关注与序列化相关的设置以及部署顺序注释。确认 #883 已部署并经过充分 soak,然后逐步启用这些选项,将 config.load_defaults 设置为 7.2,删除 defaults 文件,并运行完整测试套件;完成的要求是 CI 通过且进行一次单独的部署。

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

描述

type:infrastructure

Why

Separate from the framework bump because it is a deploy-ordering requirement, not review hygiene. Some framework defaults change the on-disk format of cached values and signed messages — cache_format_version, message_serializer and marshalling_format_version all did in 7.1, and the existing new_framework_defaults_7_1.rb carries the team's own "Does rolling deploy apply here?" annotations. A format flip must not ship in the same deploy as the framework bump, or old and new processes cannot read each other's data during the rollout.

Scope

  • Uncomment the options in new_framework_defaults_7_2.rb one group at a time
  • Bump config.load_defaults to 7.2 and delete the file once all are enabled
  • config.active_support.cache_format_version -> 7.2 only after the 7.2 code is fully deployed

For each option, check whether it affects a serialization format. If none of them do, this can be folded back into the Rails 7.2 issue — check rather than assume.

Acceptance criteria

  • Full suite green
  • load_defaults 7.2, defaults file deleted
  • Deployed separately from the framework bump

Blocked by

#883 (Rails 7.2), deployed and soaked. Blocks #886.


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