New version of hanami (2.2.0) produced dependency conflicts #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
What changed?
✳️ hanami (~> 1.2 → ~> 2.2) · Repo · Changelog
Release Notes
2.2.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 55 commits:
Prepare for v2.2.0
Use gemspec to load json gem with no warnings (#1469)
Depend on dry-system 1.1 or later (#1467)
Prepare for v2.2.0.rc1
`Dry::Operation` extensions (#1456)
Apply gateway config from parent slice (and simplify config) (#1459)
Address unused variable warning (#1461)
Add connection_options to Hanami::Providers::DB::Gateway (#1450)
Bump hanami-cli dependency to 2.2.0.beta2
Prepare for v2.2.0.beta2
Raise error if the expected database gem is not installed (#1453)
Support multiple DB gateways (#1452)
Introduce Hanami::Provider::Source (#1446)
Register ROM commands and mappers (#1448)
Don't disable prompt for select (#1444)
Remove PhantomJS binary (#1443)
Bump hanami gemspec dependencies
Add Ruby version note to CHANGELOG
Prepare for v2.2.0.beta1
Bump CI node to 20.x
Clean up list of 2.x libraries
Add test coverage badge
Remove notify-slack-action
Fix copyright date
Bump version notice in README
Drop support for Ruby 3.0
Fix CI badge source
Depend on dry-system 1.1.0.beta1 (#1436)
Require dry-configurable >= 1.2.0 (#1435)
Bump dry-inflector and rom-sql dependencies (#1434)
Set up SQL logging
Add DB provider adapter config & sensible defaults (#1430)
Allow symbol argument for label form helper (#1423)
Fix fields_for_collection attribute name when base name given (#1421)
Register db provider when only config/db/ exists (#1429)
Add db:migrate compatibility Rake task (#1428)
Do not apply config from parent ROM config object (#1425)
Make Providers::DB#database_url public (#1419)
Access providers via `#[]` method (#1418)
Apply Hanami::DB::Testing.database_url (#1415)
Replace ROM::Inflector in DB Provider (#1416)
Do not auto-register from db, relations, structs (#1413)
Configure struct_namespace for repos (#1412)
Integrate repos (#1410)
Share all config from parent DB provider to child providers
Register "db.gateway" instead of "db.connection" (#1406)
Disconnect DB on provider stop (#1407)
Cache and reuse identically-configured gateways (#1405)
Look for specific slice database URLs in ENV (#1404)
Share parent DB via `config.db.import_from_parent` (#1403)
Allow per-slice ROM setups to share plugin config (#1402)
Add .app? and .source_path to Hanami::Slice (#1399)
Add the beginnings of a :db provider (#1386)
Add hanami-db as a development dependency (#1385)
Expose the slice as the provider target (#1382)
👉 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