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

Replace annotate with annotaterb and upgrade to Rails 8.0

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

还没有人认领这个 Issue。

评估

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

调研方向

首先检查被阻塞的 issue #885 和 #884,然后查看 Rails 升级入口 bin/rails app:update 和 new_framework_defaults_8_0.rb。处理开发依赖项的替换,并检查 ActiveRecord 模型中由此产生的 schema 注释变化。完成的标准是完整测试套件通过、headers 能够干净地重新生成,并且 load_defaults 保持为 7.2。

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

描述

type:infrastructure

Why

annotate 3.2.0 declares activerecord >= 3.2, < 8.0 — a hard resolution blocker for Rails 8.0 — and is unmaintained. annotaterb 4.24.0 is the maintained fork. Since the swap exists only to unblock the framework bump, the two belong in one change.

Scope

  • Swap annotate -> annotaterb (development group only, so CI risk is near zero). Note that regenerating the # == Schema Information headers produces a large mechanical diff across all ActiveRecord models — consider doing the gem swap and the regeneration as separate commits so the regeneration does not hide anything.
  • gem "rails", "~> 8.0.0", bin/rails app:update
  • Keep load_defaults at 7.2; take new_framework_defaults_8_0.rb with everything commented

Verified Rails 8.1 resolves against this gem set, so 8.0 will too. Rails 8.1 requires PostgreSQL >= 9.5, so the current PG 12.8 is fine.

Acceptance criteria

  • Full suite green
  • Schema annotation headers regenerate cleanly
  • load_defaults still 7.2

Blocked by

#885 (Ruby 3.4.10) and #884 (Rails 7.2 defaults). Blocks #887.


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