v0.1.22

• [FIX] Error when installing migration sin Rails 7.0.0 (official) PR.

v0.1.20

• FIX: Error when referencing thread attribute after Rails upgrade [#39]

v0.1.19

• NEW: Add support for Ruby 3 [#37]

Thanks to @lewispb.

v0.1.18

• FIX: Don't freeze Active Record connection driver classes. This causes a problem with SQLite in fresh Rails apps and it's not really needed, since extending ActiveRecord classes is prevented by current anti-tampering mechanisms. 355c20a
• FIX: Don't choke when processing SQL strings with invalid encodings. 2bec352

v0.1.17

• FIX: Mark invocations to String#constantize that originate in the console as suspicious, unless they do originate in a direct command [#34]

v0.1.15

• FIX: Active resource invocations where being wrongly prevented. [#32]

v0.1.14

• NEW: Prevent tampering via reopening and altering Parser elements [#31].

v0.1.13

• FIX: Fix class loading problem with ActiveRecord::Relation class. f0a5072

v0.1.12

• FIX: Avoid loading Parser constant unless in a console session. This prevents a "class not found" error when loading console1984 code outside of the console { } hook. 2addc58

v0.1.9

• [NEW] Additional mechanisms to detect reopening forbidden classes. If a forbidden reopening materializes, it will log the command and force exiting from IRB [#28].

  Take this example:

  def my_constant
    ActiveRecord
  end
  
  class my_constant::Base
    def fake_save!(*args)
      puts "ActiveRecord::Base#save! overridden!"
    end
  end

  This code would skip existing static analysis. With the new system, code will run but will raise an error after new methods are added to the class. Because the code executes it exits immediately from IRB after flagging the command.