Did anyone resolve this issue with `Ruby 2.7.0`?

I used `rbenv` and installed Ruby v2.7.0 and then created a Rails project using `Rails v6.0.2.1`. 

Currently, by running one of

    rails s
    rails s -u puma
    rails s -u webrick

the server is up and the site is served but in the `Console` log I see two warning messages:

    local:~/rcode/rb27$ rails s
    =&gt; Booting Puma
    =&gt; Rails 6.0.2.1 application starting in development 
    =&gt; Run `rails server --help` for more startup options
    .rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/actionpack-6.0.2.1/lib/action_dispatch/middleware/stack.rb:37: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
    .rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/actionpack-6.0.2.1/lib/action_dispatch/middleware/static.rb:110: warning: The called method `initialize&#39; is defined here
    Puma starting in single mode...
    * Version 4.3.1 (ruby 2.7.0-p0), codename: Mysterious Traveller
    * Min threads: 5, max threads: 5
    * Environment: development
    * Listening on tcp://127.0.0.1:3000
    * Listening on tcp://[::1]:3000 


So, the warning messages are:

    **.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/actionpack-6.0.2.1/lib/action_dispatch/middleware/stack.rb:37: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call**

    **.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/actionpack-6.0.2.1/lib/action_dispatch/middleware/static.rb:110: warning: The called method `initialize&#39; is defined here**

I saw [this link](https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/) and there are some suggestion to switch of warnings like &quot;If you want to disable the deprecation warnings, please use a command-line argument -W:no-deprecated or add Warning[:deprecated] = false to your code.&quot; but I was thinking on little bit better solution/fix for actionpack v6.0.2.1 

All Ruby 2.7 Solutions on Gang of Coders

Total of 1 Ruby 2.7 Solutions

How to fix Rails's warning messages with Ruby 2.7.0