pkgsrc/www/ruby-actioncable70/distinfo

$NetBSD: distinfo,v 1.7 2022/07/13 14:48:48 taca Exp $

BLAKE2s (actioncable-7.0.3.1.gem) = 9e960a26580788ca047e4069786661dfa8af0d7d00f929b970473856ca8a4b61
SHA512 (actioncable-7.0.3.1.gem) = c51f255fdedfcb67633806a17b95eb226bdba22d8ed9a6f8ca76cc6a91fc2c59af93c14fafec25cad45926df78276be415ef5a8b7eca0a96846d187fd153f8fc
Size (actioncable-7.0.3.1.gem) = 44032 bytes
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:48 taca Exp $
www/ruby-actioncable70: add package version 7.0.0 Action Cable - Integrated WebSockets for Rails Action Cable seamlessly integrates WebSockets with the rest of your Rails application. It allows for real-time features to be written in Ruby in the same style and form as the rest of your Rails application, while still being performant and scalable. It's a full-stack offering that provides both a client-side JavaScript framework and a server-side Ruby framework. You have access to your full domain model written with Active Record or your ORM of choice. This is for Ruby on Rails 7.0. 2021-12-19 07:16:32 +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 (actioncable-7.0.3.1.gem) = 9e960a26580788ca047e4069786661dfa8af0d7d00f929b970473856ca8a4b61`
			`SHA512 (actioncable-7.0.3.1.gem) = c51f255fdedfcb67633806a17b95eb226bdba22d8ed9a6f8ca76cc6a91fc2c59af93c14fafec25cad45926df78276be415ef5a8b7eca0a96846d187fd153f8fc`
			`Size (actioncable-7.0.3.1.gem) = 44032 bytes`