3.1.0

• #182 Let #console live in Kernel (@gsamokovarov)
• #181 Log internal Web Console errors @schneems)
• #180 Autoload Web Console constants for faster Rails boot time (@herminiotorres)

2.3.0

This is mainly a Rails 5 compatibility release. If you have the chance, please go to 3.1.0 instead.

• #181 Log internal Web Console errors (@schneems)
• #150 Revert #150. (@gsamokovarov)

3.0.0

• #173 Revert "Change config.development_only default until 4.2.4 is released" (@gsamokovarov)
• #171 Fixed blocked IP logging (@gsamokovarov)
• #162 Render the console inside the body tag (@gsamokovarov)
• #165 Revamped integrations for CRuby and Rubinius (@gsamokovarov)

2.2.1

• #150 Change config.development_only default until 4.2.4 is released. (@gsamokovarov)

2.2.0

• #140 Add the ability to close the console on each page (@sh19910711)
• #135 Run the console only in development mode and raise warning in tests (@frenesim)
• #134 Force development only web console by default (@gsamokovarov)
• #123 Replace deprecated alias_method_chain with alias_method (@jonatack)

2.1.3

• Fix remote code execution vulnerability in Web Console. CVE-2015-3224.

2.1.2

• #115 Show proper binding when raising an error in a template (@gsamokovarov)
• #114 Fix templates non rendering, because of missing template suffix (@gsamokovarov)

2.1.1

• #112 Always allow application/x-www-form-urlencoded content type (@gsamokovarov)

2.1.0

• #109 Revamp unavailable session response message (@gsamokovarov)
• #107 Fix pasting regression for all browsers (@parterburn)
• #105 Lock scroll bottom on console window resize (@noahpatterson)
• #104 Always whitelist localhost and inform users why no console is displayed (@gsamokovarov)
• #100 Accept text/plain as acceptable content type for Puma (@gsamokovarov)
• #98 Add arbitrary big z-index to the console (@bglbruno)
• #88 Spelling fixes (@jeffnv)
• #86 Disable autofocus when initializing the console (@ryandao)
• #84 Allow Rails 5 as dependency in gemspec (@jonatack)
• #69 Introduce middleware for request dispatch and console rendering (@gsamokovarov)

2.0.0

Debugging tool for the error pages

An interactive console is launched automatically in the default Rails error
page. It makes it easy to inspect the stack trace and execute Ruby code in the stack
trace's bindings.

(Check out better_errors as a great alternative for any Rack application!)

Debugging tool in your controllers and views

Drop <%= console %> anywhere in a view to launch an interactive console
session and execute code in it. Drop console anywhere in a controller and do
the same in the context of the controller action.

No more VT100 web terminal emulators

This feature fall behind as it didn't see that much use.