Ruby on Rails 7.1: What's New, Release History & Support Lifecycle

What Is New in Ruby on Rails 7.1

How can I get a ready-to-run Docker setup for a new Rails 7.1 app?

Rails 7.1 now scaffolds Dockerfiles automatically when you run rails new.

• The generated Dockerfile builds a minimal Ruby image with your app code.
• A docker-compose.yml is also added for easy service orchestration.
• These files are intended for production deployment, not for local development.

# Build and run the container
docker build -t myapp .
docker volume create app-storage
docker run --rm -it -v app-storage:/rails/storage -p 3000:3000 \
  --env RAILS_MASTER_KEY=<your-config-master-key> myapp

# Open a console inside the container
docker run --rm -it -v app-storage:/rails/storage \
  --env RAILS_MASTER_KEY=<your-config-master-key> myapp console

For multi-platform images, use docker buildx as shown in the generated README.

What new ActiveRecord helpers help keep data clean and secure in Rails 7.1?

Rails 7.1 introduces normalizes and generates_token_for macros on ActiveRecord::Base.

• normalizes automatically sanitizes attribute values on assignment and when used in queries.
• generates_token_for creates purpose-specific, expirable tokens that can embed record data for one-time actions.

class User < ApplicationRecord
  normalizes :email, with: ->(e){ e.strip.downcase }
  normalizes :phone, with: ->(p){ p.delete("^0-9").delete_prefix("1") }

  generates_token_for :password_reset, expires_in: 15.minutes do
    password_salt&.last(10)
  end
end

# Normalization in action
User.create(email: "  [email protected]\n").email # => "[email protected]"

# Token usage
token = user.generate_token_for(:password_reset)
User.find_by_token_for(:password_reset, token) # => user

These helpers reduce boilerplate and make security-critical logic declarative.

How do I enqueue a batch of background jobs with a single call in Rails 7.1?

The new ActiveJob.perform_all_later method lets you push many jobs at once without triggering per-job callbacks.

• Pass an array of job instances or a list of arguments.
• Adapters that support enqueue_all (e.g., Sidekiq) will use bulk push for optimal performance.
• A distinct enqueue_all.active_job event is emitted for monitoring.

# Enqueue two jobs directly
ActiveJob.perform_all_later(MyJob.new("hello", 42), MyJob.new("world", 0))

# Enqueue a dynamic batch
user_ids = User.pluck(:id)
jobs = user_ids.map { |id| NotifyUserJob.new(user_id: id) }
ActiveJob.perform_all_later(jobs)

This method is especially useful for data-migration scripts or bulk email campaigns.

Which async query methods and composite primary key support should I adopt in Rails 7.1?

Rails 7.1 adds a family of async_* query helpers and native composite primary key handling.

• async_count, async_sum, async_average, etc., return an ActiveRecord::Promise that resolves when you call value.
• Composite primary keys are inferred from the schema and work with #reload, #update, and association foreign keys via the query_constraints macro.

# Asynchronous count
promise = Post.where(published: true).async_count
# Do other work ...
published = promise.value # => integer count

# Composite primary key example
class TravelRoute < ApplicationRecord
  query_constraints :origin, :destination
end

class TravelRouteReview < ApplicationRecord
  belongs_to :travel_route,
    query_constraints: [:travel_route_origin, :travel_route_destination]
end

Use async helpers for heavy aggregates and composite keys for join tables that lack a single id column.