Log Message:
devel/ruby-flexmock: update to 3.0.1

3.0.0 (2024-07-18)

* Added keyword argument and explicit proc support.  Keyword argument
  support is Ruby 3.0+ only, getting the support to work on Ruby 2.7 deemed
  to be too complicated.  See the release notes for 2.4 below for
  information about how migration can be done smoothly

* with now expects all expected keyword arguments to be explicitly given in
  a natural way, for instance:

	mock.should_receive(:m).with("some", "args", with: 42)

  The values given to the arguments can be any matcher valid for the
  positional arguments

* note that not giving any keyword arguments to with is interpreted as a
  negative (no keyword arguments are expected), and will fail if some
  arguments are given.  Call with_any_kw_args after the with if you do not
  desire validation of keyword arguments:

	mock.should_receive(:m).with("some", "args").with_any_kw_args

* for more complex matches, pass a match object to the with_kw_args method.
  For instance, to match only some keyword arguments, do

	mock.should_receive(:m).with("some", \ 
"args").with_kw_args(hsh(with: 42))

* this release also makes matching procs explicit.  Instead of passing Proc
  at the end of with as in 2.x, call with_block or with_no_block.  If
  neither are called, flexmock won't validate either way (ignore whether or
  not a block was given).  The default is to not match blocks, that is
  working

* The default is to assume that blocks are optional (i.e. flexmock will
  match either way).  Nonetheless, the method with_optional_block is
  implemented to help migration from flexmock 2.4.0 (but is a no-op).

3.0.1 (2024-09-09)

* fix: handling of blocks in pass_thru (v3.0)