This releases fixes Ruby 3.0 compatibility (meaning running under 3.0, new syntax is not supported yet).
Changes since 4.10.0:
- Declare REXML as a dependency (Ruby 3.0 compatibility)
Sexp#[..](Ruby 3.0 compatibility)
- Prevent render loops when template names are absolute paths (#1536)
- Ensure RubyParser is passed file path as a String (#1534)
- Support new Haml 5.2.0 escaping method (#1517)
REXML as an Explicit Dependency
In Ruby 3.0, REXML has become a ‘bundled’ gem. It is distributed with Ruby, but if Bundler is involved then it needs to be declared as an explicit dependency.
If you like minimal dependencies, you can always use the
brakeman-min gem which declares only strict dependencies.
Avoid Slicing with Sexp#
Sexp subclasses from
Array no longer returns subclasses from methods that create new arrays.
Brakeman was unfortunately using
Sexp# with ranges (e.g.
s(:a, :b, :c)[1..-1]), which runs into this behavior.
Sexp#sexp_body method already exists to properly slice and return a
Recursive Renders with Absolute Paths
Brakeman has long been able to detect recursive render loops, but that detection did not work if the partial name was an ‘absolute’ path.
This is now fixed!
Ensure RubyParser Path is a String
In some cases, the parser was given a
Brakeman::FilePath for the file name.
This only caused an issue in some weird corner cases, but it was wrong nonetheless.
Brakeman::FileParser will ensure the file name is passed as a string.
Support Haml 5.2
Haml 5.2.0 introduced a new method for escaping output, which caused some false positives.
(Note this was avoided in Brakeman 4.10.0 by bundling an earlier version of Haml.)
The SHA256 sums for this release are:
e40451080554884a63d73a2933c36518a3cf7a2bb471e6d864ce39a9d3455c98 brakeman-4.10.1.gem ec69e04e087b74862629e952d7817dd7b73e30810166e01d69d24d7164101455 brakeman-lib-4.10.1.gem 3deee68eadd8eb6850254a8e753d6bbe933194c883f12a2455bdf5fd97b1eba2 brakeman-min-4.10.1.gem
Thank you to everyone who reported bugs and contributed to this release!
Please report any issues with this release. Take a look at this guide to reporting Brakeman problems.
Follow @brakeman on Twitter and hang out on Gitter for questions and discussion.