Skip to content

Support Rails 8 / Ruby 3.4 - #1

Merged
adz624 merged 5 commits into
masterfrom
support-rails-8-ruby-3.4
Oct 27, 2026
Merged

adz624 merged 5 commits into
masterfrom
support-rails-8-ruby-3.4

Conversation

@adz624

@adz624 adz624 commented Sep 24, 2026

Copy link
Copy Markdown
Member

Summary

Support Rails 8 and Ruby 3.4.

  • Widen gemspec / dependency constraints where needed
  • Update CI / Appraisal gemfiles for Rails 8 and Ruby 3.4
  • Keep existing Rails/Ruby matrices working

Test plan

  • CI green on new matrix
  • Spot-check in EIP or host app if relevant

Notes

  • Do not publish gem to RubyGems from this PR
  • Do not merge until reviewed

adz624 and others added 5 commits September 24, 2026 12:45
- Widen activesupport to >= 6.0, < 8.2
- Remove required_ruby_version upper bound < 3.4.0 (now >= 2.7.0)
- Add gemfiles for Rails 8.0.5.1 and 8.1.3.1 × Ruby 3.3/3.4
- Extend GitHub Actions matrix with Ruby 3.3/3.4 × Rails 8.0/8.1
- Add csv runtime dependency (Ruby 3.4 stdlib extraction)
- Bump version to 1.2.1
Stale PATH gemspecs in several gemfiles/*.lock omitted the new csv
runtime dependency, so frozen bundle install failed on CI.
Locks regenerated on Ruby 3.3 pulled gems (i18n 1.15, zeitwerk 2.8,
connection_pool 3, ffi platform) incompatible with 2.7/3.0/3.1.
Remove those locks so CI resolves per matrix Ruby (same as unlocked
3.2 gemfiles). Keep refreshed 3.3/8.0 lock (csv PATH fix).
@sensui624

Copy link
Copy Markdown
Contributor

已在此分支新增:

  • .github/workflows/publish.yml(RubyGems Trusted Publishing)
  • CLAUDE.md(「每個 PR 都必須跳版號」的發版規則)

合併前請先完成以下設定,否則發佈會失敗或不受保護:

  1. 在 rubygems.org 的 export_to 設定 Trusted Publisher:repository superlanding/export_to、workflow publish.yml、environment gem-publish。
  2. 在 GitHub 建立 gem-publish environment,並限制只有 master 分支可部署。
  3. 設定 master ruleset:只有真人開發者可以推/合併,AI 帳號只能開 branch 與 PR。

⚠️ 注意:此分支版本是 1.2.1,而 RubyGems 上目前是 1.2.0。設定完成後,合併到 master 會立即發佈 1.2.1。

@adz624
adz624 merged commit d411c6a into master Oct 27, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants