Log message:
lang/ruby: start update of Ruby on Rails 7.0

Start update of Ruby on Rails to 7.0.4.

Log message:
www/ruby-rails61: update to 6.1.7

Ruby on Rails 6.1.7 release on 9th September 2022.
Active Record and Active Storage are updated:

Active Record

* Symbol is allowed by default for YAML columns

  Étienne Barrié

* Fix ActiveRecord::Store to serialize as a regular Hash

  Previously it would serialize as an
  ActiveSupport::HashWithIndifferentAccess which is wasteful and cause
  problem with YAML safe_load.

  Jean Boussier

* Fix PG.connect keyword arguments deprecation warning on ruby 2.7

  Fixes .

  Nikita Vasilevsky

Active Storage

* Respect Active Record's primary_key_type in Active Storage
  migrations. Backported from 7.0.

  fatkodima

Log message:
www/ruby-rails60: update to 6.0.6

Ruby on Rails 6.0.6 release on 9th September 2022 and
Active Record is only updated.

databases/ruby-activerecord60

* Symbol is allowed by default for YAML columns

  Étienne Barrié

Log message:
lang/ruby: better handling for dependency

Instead of "expr" command, make commands to make's variable and
later evaluate with :sh modifier.

Thank Jonathan Perkin provides problem and solution.

Log message:
lang/ruby/rails.mk: use expr instead of ${EXPR}

Since rails.mk might be used before ${EXPR} is defined, use expr
instead of ${EXPR}.

Log message:
ruby: Pull in libiconv.

Log message:
www/ruby-rails70: update to 7.0.3.1

Rails 7.0.3.1 (2022-07-12) updates databases/ruby-activerecord70 only.

databases/ruby-activerecord70

* Change ActiveRecord::Coders::YAMLColumn default to safe_load

  This adds two new configuration options The configuration options are as
  follows:

	o config.active_storage.use_yaml_unsafe_load

  When set to true, this configuration option tells Rails to use the old
  "unsafe" YAML loading strategy, maintaining the existing behavior but
  leaving the possible escalation vulnerability in place.  Setting this
  option to true is *not* recommended, but can aid in upgrading.

	o config.active_record.yaml_column_permitted_classes

  The "safe YAML" loading method does not allow all classes to be
  deserialized by default.  This option allows you to specify classes deemed
  "safe" in your application.  For example, if your application uses Symbol
  and Time in serialized data, you can add Symbol and Time to the allowed
  list as follows:

	config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]

  [CVE-2022-32224]

Log message:
www/ruby-rails61: update to 6.1.6.1

Rails 6.1.6.1 (2022-07-12) updates databases/ruby-activerecord61 only.

databases/ruby-activerecord61

* Change ActiveRecord::Coders::YAMLColumn default to safe_load

  This adds two new configuration options The configuration options are as
  follows:

	o config.active_storage.use_yaml_unsafe_load

  When set to true, this configuration option tells Rails to use the old
  "unsafe" YAML loading strategy, maintaining the existing behavior but
  leaving the possible escalation vulnerability in place.  Setting this
  option to true is *not* recommended, but can aid in upgrading.

	o config.active_record.yaml_column_permitted_classes

  The "safe YAML" loading method does not allow all classes to be
  deserialized by default.  This option allows you to specify classes deemed
  "safe" in your application.  For example, if your application uses Symbol
  and Time in serialized data, you can add Symbol and Time to the allowed
  list as follows:

	config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]

  [CVE-2022-32224]

Log message:
www/ruby-rails60: update to 6.0.5.1

Rails 6.0.5.1 (2022-07-12) updates databases/ruby-activerecord60 only.

databases/ruby-activerecord60

* Change ActiveRecord::Coders::YAMLColumn default to safe_load

  This adds two new configuration options The configuration options are as
  follows:

	o config.active_storage.use_yaml_unsafe_load

  When set to true, this configuration option tells Rails to use the old
  "unsafe" YAML loading strategy, maintaining the existing behavior but
  leaving the possible escalation vulnerability in place.  Setting this
  option to true is *not* recommended, but can aid in upgrading.

	o config.active_record.yaml_column_permitted_classes

  The "safe YAML" loading method does not allow all classes to be
  deserialized by default.  This option allows you to specify classes deemed
  "safe" in your application.  For example, if your application uses Symbol
  and Time in serialized data, you can add Symbol and Time to the allowed
  list as follows:

	config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]

  [CVE-2022-32224]

Log message:
www/ruby-rails52: update to 5.2.8.1

Rails 5.2.8.1 (2022-07-12) updates databases/ruby-activerecord52 only.

databases/ruby-activerecord52

* Change ActiveRecord::Coders::YAMLColumn default to safe_load

  This adds two new configuration options The configuration options are as
  follows:

	o config.active_storage.use_yaml_unsafe_load

  When set to true, this configuration option tells Rails to use the old
  "unsafe" YAML loading strategy, maintaining the existing behavior but
  leaving the possible escalation vulnerability in place.  Setting this
  option to true is *not* recommended, but can aid in upgrading.

	o config.active_record.yaml_column_permitted_classes

  The "safe YAML" loading method does not allow all classes to be
  deserialized by default.  This option allows you to specify classes deemed
  "safe" in your application.  For example, if your application uses Symbol
  and Time in serialized data, you can add Symbol and Time to the allowed
  list as follows:

	config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]

  [CVE-2022-32224]