From c975c096f6d140a6bcdc69b450072a2be3dc58d2 Mon Sep 17 00:00:00 2001 From: Andrey Novikov Date: Thu, 20 Oct 2022 00:59:09 +0900 Subject: [PATCH] Remove outdated entry from 6.0-Upgrade.md about server initialization signature (#2992) [ci skip] --- 6.0-Upgrade.md | 1 - 1 file changed, 1 deletion(-) diff --git a/6.0-Upgrade.md b/6.0-Upgrade.md index 0eee1d67..8e8724aa 100644 --- a/6.0-Upgrade.md +++ b/6.0-Upgrade.md @@ -45,7 +45,6 @@ Check the following list to see if you're depending on any of these behaviors: 1. We've removed the following constants: `Puma::StateFile::FIELDS`, `Puma::CLI::KEYS_NOT_TO_PERSIST_IN_STATE` and `Puma::Launcher::KEYS_NOT_TO_PERSIST_IN_STATE`, and `Puma::ControlCLI::COMMANDS`. 1. We no longer support Ruby 2.2, 2.3, or JRuby on Java 1.7 or below. 1. The behavior of `remote_addr` has changed. When using the set_remote_address header: "header_name" functionality, if the header is not passed, REMOTE_ADDR is now set to the physical peeraddr instead of always being set to 127.0.0.1. When an error occurs preventing the physical peeraddr from being fetched, REMOTE_ADDR is now set to the unspecified source address ('0.0.0.0') instead of to '127.0.0.1' -1. If you are creating your own Puma::Server objects, it's initialize signature has changed. In 5.x and below, it was `def initialize(app, events=Events.stdio, options={})`. Now it is `def initialize(app, log_writer=LogWriter.stdio, events=Events.new, options = {})`. Then, update your Gemfile: