CVE and update status of the FreeBSD ports tree4,826 unaddressed CVEs in 618 portsAll times are CET

Port details

devel/rubygem-activejob818.1.3.1

Declare job classes that can be run by a variety of queuing backends

0
unaddressed
0
VuXML only, still affected
0
fixed
Maintainer
sunpoet@FreeBSD.org
Packages
rubygem-activejob81 8.1.3.1
Upstream
Higher version available: 8.1.4
CPE
rubyonrails:active_job from the port
WWW
https://github.com/rails/rails/tree/main/activejob
Links
cgit · VuXML

Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE

None. There is no CVE without a VuXML entry for this version.

VuXML only (0) · listed, port not fixed yet

None. pkg audit reports nothing for this version.

Fixed (0)

No VuXML entries for this package.

Commits (5)

Po-Chuan Hsieh (sunpoet) · 8.1.3.1
devel/rubygem-activejob81: Update to 8.1.3.1

Changes:	https://github.com/rails/rails/releases
85f075af95
Po-Chuan Hsieh (sunpoet) · 8.1.3
devel/rubygem-activejob81: Update to 8.1.3

Changes:	https://github.com/rails/rails/releases
cc0e61d256
Po-Chuan Hsieh (sunpoet) · 8.1.2
devel/rubygem-activejob81: Update to 8.1.2

Changes:	https://github.com/rails/rails/releases
0c4c09713c
Po-Chuan Hsieh (sunpoet) · 8.1.1
devel/rubygem-activejob81: Update to 8.1.1

Changes:	https://github.com/rails/rails/releases
4c0c49b33b
Po-Chuan Hsieh (sunpoet) · 8.1.0
devel/rubygem-activejob81: Add rubygem-activejob81 8.1.0

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.
5a8acfd8df