kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/ruby-activejob70/distinfo

6 lines
360 B
Text
Raw Normal View History

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]
2022-07-13 16:48:47 +02:00
$NetBSD: distinfo,v 1.7 2022/07/13 14:48:47 taca Exp $
devel/ruby-activejob70: add package version 7.0.0 Active Job - Make work happen later Active Job is a framework for declaring jobs and making them run on a variety of queuing backends. These jobs can be everything from regularly scheduled clean-ups, to billing charges, to mailings -- anything that can be chopped up into small units of work and run in parallel. It also serves as the backend for Action Mailer's #deliver_later functionality that makes it easy to turn any mailing into a job for running later. That's one of the most common jobs in a modern web application: sending emails outside the request-response cycle, so the user doesn't have to wait on it. The main point is to ensure that all Rails apps will have a job infrastructure in place, even if it's in the form of an "immediate runner". We can then have framework features and other gems build on top of that, without having to worry about API differences between Delayed Job and Resque. Picking your queuing backend becomes more of an operational concern, then. And you'll be able to switch between them without having to rewrite your jobs. This is for Ruby on Rails 7.0.
2021-12-19 06:53:19 +01:00
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]
2022-07-13 16:48:47 +02:00
BLAKE2s (activejob-7.0.3.1.gem) = 3b50837931f9662bb3b009622db793fe2c8951b6c22b0d10255868b97b048032
SHA512 (activejob-7.0.3.1.gem) = 724dcea780fce091fb3323c64fb4b3bf65d52591c2ca59bd50816c9cbecda7cd4239ba42a2451be47a5aceff39f8482a02ad52637c31a638d2737c79e67e94d1
Size (activejob-7.0.3.1.gem) = 33280 bytes
Reference in a new issue Copy permalink