./devel/ruby-activejob61, Job classes that can be run by a variety of queueing backends

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 6.1.7.10, Package name: ruby32-activejob61-6.1.7.10, Maintainer: pkgsrc-users

Active Job is a framework for declaring jobs and making them run on a
variety of queueing 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, really.

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 of 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 6.1.

Master sites:

Filesize: 32 KB

Version history: (Expand)

CVS history: (Expand)


   2024-02-24 15:42:41 by Takahiro Kambe | Files touched by this commit (17) | Package updated
Log message:
www/rails61: update to 6.1.7.7

Update rails61 and related pacakges to 6.1.7.7
This includes security fix for CVE-2024-26144, devel/ruby-activestorage61.

Active Storage

* Disables the session in ActiveStorage::Blobs::ProxyController and
  ActiveStorage::Representations::ProxyController in order to allow caching
  by default in some CDNs as CloudFlare

  Fixes #44136

  Bruno Prieto
   2023-08-26 17:23:29 by Takahiro Kambe | Files touched by this commit (14) | Package updated
Log message:
www/ruby-rails61: update to 6.1.7.6

6.1.7.5 (2023-08-22)

Active Support

* Use a temporary file for storing unencrypted files while editing
  [CVE-2023-38037]

6.1.7.6 (2023-08-22)

* No changes between this and 6.1.7.5.  This release was just to fix file
  permissions in the previous release.
   2023-06-27 15:35:19 by Takahiro Kambe | Files touched by this commit (14) | Package updated
Log message:
www/rails61: update to 6.1.7.4

Rails 6.1.7.4 (2023-06-26)

Action Pack

*   Raise an exception if illegal characters are provide to redirect_to
    [CVE-2023-28362]

    *Zack Deveau*
   2023-03-15 14:31:49 by Takahiro Kambe | Files touched by this commit (15) | Package updated
Log message:
www/ruby-rails61: update to 6.1.7.3

6.1.7.3 (2023-03-13)

Active Support

* Implement SafeBuffer#bytesplice

  [CVE-2023-28120]

Action View

* Ignore certain data-* attributes in rails-ujs when element is
  contenteditable

  [CVE-2023-23913]
   2023-01-25 14:27:10 by Takahiro Kambe | Files touched by this commit (14) | Package updated
Log message:
www/ruby-rails61: update to 6.1.7.2

Rails 6.1.7.2 (2023-01-24)

www/ruby-actionpack61

*   Fix `domain: :all` for two letter TLD

    This fixes a compatibility issue introduced in our previous security
    release when using `domain: :all` with a two letter but single level top
    level domain domain (like `.ca`, rather than `.co.uk`).
   2023-01-19 15:31:11 by Takahiro Kambe | Files touched by this commit (15) | Package updated
Log message:
www/ruby-rails61: update to 6.1.7.1

Rails 6.1.7.1 (2023-01-17)

devel/ruby-activesupport61

* Avoid regex backtracking in Inflector.underscore

    [CVE-2023-22796]

www/ruby-actionpack61

* Avoid regex backtracking on If-None-Match header

  [CVE-2023-22795]

* Use string#split instead of regex for domain parts

  [CVE-2023-22792]

databases/ruby-activerecord61

* Make sanitize_as_sql_comment more strict

  Though this method was likely never meant to take user input, it was
  attempting sanitization. That sanitization could be bypassed with
  carefully crafted input.

  This commit makes the sanitization more robust by replacing any
  occurrances of "/*" or "*/" with "/ *" or \ 
"* /". It also performs a
  first pass to remove one surrounding comment to avoid compatibility
  issues for users relying on the existing removal.

  This also clarifies in the documentation of annotate that it should not
  be provided user input.

  [CVE-2023-22794]

* Added integer width check to PostgreSQL::Quoting

  Given a value outside the range for a 64bit signed integer type
  PostgreSQL will treat the column type as numeric. Comparing
  integer values against numeric values can result in a slow
  sequential scan.

  This behavior is configurable via
  ActiveRecord::Base.raise_int_wider_than_64bit which defaults to true.

  [CVE-2022-44566]
   2022-09-10 10:24:42 by Takahiro Kambe | Files touched by this commit (14) | Package updated
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
   2022-07-13 16:46:24 by Takahiro Kambe | Files touched by this commit (15) | Package updated
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]