New version of hanami (2.3.0) produced dependency conflicts

[depfu]

---

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

---

We've tried to upgrade a dependency and got errors running Bundler. It looks like there is a version conflict between two or more dependencies. Depfu doesn't try to solve these, as this would mean to update more than one dependency at a time.

Please take a look at the exact failure to figure out if this is something you need to work on.

The bundler error message was:

Bundler could not find compatible versions for gem "parser":
  In Gemfile:
    reek was resolved to 6.1.4, which depends on
      parser (~> 3.2.0)

    rubocop was resolved to 1.59.0, which depends on
      rubocop-ast (< 2.0, >= 1.30.0) was resolved to 1.31.2, which depends on
        parser (>= 3.3.0.4)

What changed?

✳️ hanami (~> 1.2 → ~> 2.3) · Repo · Changelog

Release Notes

2.3.0 (from changelog)

Added

• Add resources and resource methods to the routes DSL. (@afomera and @timriley in #1542 and #1548)

  resources :users

  # Generates:
  # GET /users users.index
  # GET /users/new users.new
  # POST /users users.create
  # GET /users/:id users.show
  # GET /users/:id/edit users.edit
  # PATCH /users/:id users.update
  # DELETE /users/:id users.destroy

  resource :profile
  # Generates (singular, no index):
  # GET /profile/new profile.new
  # POST /profile profile.create
  # GET /profile profile.show
  # GET /profile/edit profile.edit
  # PATCH /profile profile.update
  # DELETE /profile profile.destroy

Changed

• Enable body parsing middleware by default. (@timriley in #1549)

  This will parse multipart form upload bodies in requests with content type of multipart/form-data, and JSON bodies in requests with content types of application/json or application/vnd.api+json.

• For standard logging, use block-based API to provide log payloads, so that log payloads are not generated if the log severity is less than the configured log level. (@p8 in #1550)

Fixed

• Avoid errors when eagerloading Zeitwerk (or when running bin/rails zeitwerk:check if your Hanami app is embedded within Rails) by skipping autoloading for extension files that may depend on non-installed gems. (@timriley in #1498)
• Only extend Dry::Operation for Hanami’s database layer when the hanami-db gem is bundled. (@timriley in #1490)
• Address deprecation warnings from previous usage of JSON.fast_generate. (@krzykamil in #1546)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 51 commits:

• Fix loading of router extensions
• Bump Hanami dependency versions
• Update CHANGELOG for v2.3.0
• Use latest repo names in CHANGELOG links
• Fix misnaming of “create” resource routes (#1554)
• Link to the CHANGELOGS of related Hanami gems (#1553)
• Prepare for v2.3.0
• Set version for API docs
• Do not autoload files that may depend on non-installed gems (#1498)
• Don't generate logging payload if severity is less than logger level (#1550)
• Enable body parser middleware by default (#1549)
• Resource-oriented routes (#1548)
• Use new prefixed repo names in Gemfile (#1547)
• Only auto-inject db.rom into operations when hanami-db is bundled (#1490)
• Remove Ruby version information from README
• Replace fast_generate with generate (json) (#1546)
• Prepare for v2.3.0.beta2
• Update gem metadata
• Require Ruby 3.2
• Use new action formats config (#1544)
• Show relative path in MissingActionError (#1445)
• Remove injected `settings` from view context (#1537)
• Prepare for v2.3.0.beta1
• Prepare CHANGELOG for v2.3.0.beta1
• Avoid early loading of routes file (#1539)
• Add `console` to configuration (#1540)
• Add Rack 2/3 to CI build matrix (#1532)
• Update year in README.md (#1531)
• Support Rack 3 (#1493)
• Fix inference of root for deeply nested repos (#1478)
• Add support for single-character slice names (#1528)
• Allow Deps mixin to work in repos (#1523)
• Add tags for zeitwerk loaders (#1497)
• Support optional nonce in Rack requests, CSP header rules and view helpers (#1503)
• Don't capture on absolute URL detection (#1519)
• Fix deprecation warning about URI::DEFAULT_PARSER. (#1518)
• Ensure DB connections are closed in app_integration tests (#1514)
• Update Contact section to point Chat URL to Discord (#1515)
• Fix redundant "Unreleased" section in CHANGELOG
• Overhaul CONTRIBUTING.md (#1506)
• Look up APP_ENV as a fallback after HANAMI_ENV (#1495)
• Update error message assertion for latest Rack (#1512)
• Remove un-used shared_examples (#1508)
• Add keepalive action to CI and stop redundant builds (#1510)
• Make Node steps in ci.yml consistent with assets repos
• Upgrade actions to latest versions (#1507)
• Make README more up to date (#1501)
• Use version agnostic URL to API doc in README (#1491) (#1496)
• Add Ruby 3.4 support (#1492)
• Fix typo (#1485)
• Simpilify README, add hanami-db link (#1481)

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #35.