[ruby] New version of simplecov (0.22.0) produced dependency conflicts#47
Merged
Conversation
Member
|
@depfu rebase |
a4d8b76 to
a1b684c
Compare
Codecov Report
@@ Coverage Diff @@
## main #47 +/- ##
==========================================
- Coverage 55.55% 52.63% -2.93%
==========================================
Files 2 2
Lines 18 19 +1
==========================================
Hits 10 10
- Misses 8 9 +1 see 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
a1b684c to
efaa456
Compare
Member
|
As I understand, the fix for TruffleRuby is in v23.0, and the latest version of Docker package is still 22.3.1: graalvm/container#80 |
Member
|
@depfu rebase |
efaa456 to
ba5db10
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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?
✳️ simplecov (~> 0.21.0 → ~> 0.22.0) · Repo · Changelog
Release Notes
0.22.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 34 commits:
Add missing closing parenthesis)Merge pull request #1041 from simplecov-ruby/co-prepare-0.22.0Hmm, ok maybe I actually have to bump the version here as wellRun bundle lock in each test project directoryGo back to prior bundler and json formatter versions, to make CI happyBump to latest bundler version for developmentBump version, update changelogMerge pull request #1034 from nhtruong/mainMerge pull request #1037 from mame/coverage-for-evalShow a warning for the case where coverage for eval is unavailableSupport coverage for evalMerge pull request #1035 from mame/support-ruby-3Drop 2.6 from the CI and update README.mdJRuby does not support branch coverageDrop Ruby 2.5Update gems of test_projects/rails/rspec_rails/Gemfile for new rubiesAvoid double Coverage.startBumped Rack version to 2.2.3.1Reduce memory usage while generating reporttest: Use unreleased version of apparitionJRuby 9.3 seeems to need some more love as well.CI: leave 3.1 out of the matrix for nowbuild: add matrix gem, not incl in 3.1build: Collapse two CI stepsAdd earlier link to spring section (#1010)Update gem to avoid warnings and do not install docs (#1011)Unify windows and bash .gitignore additionAdd needed require line for CSV exampleFix grammar and code formatting in READMEminor gem updatesDeactivate rubocop extension suggestionsUpgrade rubocopFix error in jruby CI job via gem upgradesUpgrade minitest so that we can run our tests against ruby-trunkDepfu 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