NoMethodError: private method `warn' called for class ActiveSupport::Deprecation

This issue is a (choose one):

• Problem/bug report.
• Feature request.
• Request for support. Note: Please try to avoid submitting issues for support requests. Use Gitter instead.

Checklist before submitting:

• I've searched for an existing issue.
• I've asked my question on Gitter and have not received a satisfactory answer.
• I've included a complete bug report template. This step helps us and allows us to see the bug without trying to reproduce the problem from your description. It helps you because you will frequently detect if it's a problem specific to your project.
• The feature I'm asking for is compliant with the JSON:API spec.

Description

I'm trying to upgrade to Rails 7.2 and when I run rails app:update the process failed with this error:

$ rails app:update
...
       rails  active_storage:update
bin/rails aborted!
NoMethodError: private method `warn' called for class ActiveSupport::Deprecation (NoMethodError)

        ActiveSupport::Deprecation.warn "In #{name} you exposed a `has_one` relationship "\
                                  ^^^^^
/Users/jgreen/projects/seshy-api/app/resources/jsonapi/v1/user_resource.rb:9:in `<class:UserResource>'
/Users/jgreen/projects/seshy-api/app/resources/jsonapi/v1/user_resource.rb:1:in `<main>'
/Users/jgreen/projects/seshy-api/config/routes.rb:24:in `block (3 levels) in <main>'
/Users/jgreen/projects/seshy-api/config/routes.rb:10:in `block (2 levels) in <main>'
/Users/jgreen/projects/seshy-api/config/routes.rb:9:in `block in <main>'
/Users/jgreen/projects/seshy-api/config/routes.rb:1:in `<main>'
/Users/jgreen/projects/seshy-api/config/environment.rb:5:in `<main>'
Tasks: TOP => active_storage:update => environment
(See full trace by running task with --trace)

Der Fehler tritt beim Laden von app/resources/jsonapi/v1/user_resource.rb über config/routes.rb und config/environment.rb auf; reproduziere ihn, indem du rails app:update unter Rails 7.2 ausführst, und untersuche den im Trace angezeigten Deprecation-Aufruf. Als erledigt gilt die Aufgabe, wenn die Ressource geladen wird und der Update-Task ohne NoMethodError abgeschlossen wird.