diff --git a/devel/rubygem-activejob70/Makefile b/devel/rubygem-activejob70/Makefile
index 698565c439e5..b16223af2706 100644
--- a/devel/rubygem-activejob70/Makefile
+++ b/devel/rubygem-activejob70/Makefile
@@ -1,27 +1,28 @@
 PORTNAME=	activejob
 PORTVERSION=	7.0.3.1
 CATEGORIES=	devel rubygems
 MASTER_SITES=	RG
 PKGNAMESUFFIX=	70
 
 MAINTAINER=	sunpoet@FreeBSD.org
 COMMENT=	Declare job classes that can be run by a variety of queuing backends
-WWW=		https://github.com/rails/rails/tree/main/activejob
+WWW=		https://github.com/rails/rails/tree/main/activejob \
+		https://rubyonrails.org/
 
 LICENSE=	MIT
 LICENSE_FILE=	${WRKSRC}/MIT-LICENSE
 
-RUN_DEPENDS=	rubygem-activesupport70>=${PORTVERSION}:devel/rubygem-activesupport70 \
+RUN_DEPENDS=	rubygem-activesupport70>=${PORTVERSION}<${PORTVERSION}_99:devel/rubygem-activesupport70 \
 		rubygem-globalid-rails70>=0.3.6:databases/rubygem-globalid-rails70
 
 USES=		cpe gem
 USE_RUBY=	yes
 
 NO_ARCH=	yes
 
 CPE_VENDOR=	rubyonrails
 CPE_PRODUCT=	active_job
 
 PORTSCOUT=	limit:^7\.0\.
 
 .include <bsd.port.mk>
diff --git a/devel/rubygem-activejob70/pkg-descr b/devel/rubygem-activejob70/pkg-descr
index 61cb4267ad4c..d618ca834e3c 100644
--- a/devel/rubygem-activejob70/pkg-descr
+++ b/devel/rubygem-activejob70/pkg-descr
@@ -1,18 +1,16 @@
 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.
-
-See also: https://rubyonrails.org/