Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency minitest-reporters to ">= 1.5.0", "< 1.7.2" #26133

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Jun 20, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
minitest-reporters "~> 1.5.0" -> ">= 1.5.0", "< 1.7.2" age adoption passing confidence

Release Notes

CapnKernul/minitest-reporters (minitest-reporters)

v1.7.1

Compare Source

  • Fixed logic of new suppress_inline_failure_output. This option was doing the opposite of what it intended to do.
    #​354

v1.7.0

Compare Source

  • Minor documentation improvements #​343
  • Fixed homepage link in gemspec #​333 contributed by andyw8
  • Added Ruby 3.2 to the CI matrix #​335 contributed by petergoldstein
  • Updated JUnitReporter to output a failure screenshot path when included in the minitest result #​346 contributed by matteeyah
  • Fixed backwards fraction in ProgressReporter default format #​348 contributed by notEthan
  • Added option suppress_inline_failure_output to SpecReporter to provide an explicit switch, separate from print_failure_summary, for suppressing inline failure messages. Until this change, the print_failure_summary would do both: print a failure/error summary after all tests run and suppress the inline failure messages. With this change print_failure_summary will just add a summary at the end of a test run, and it will no longer suppress the inline failure messages. #​352 contributed by rthbound

v1.6.1

Compare Source

  • Replaced use of MiniTest constant with Minitest #​345 contributed by istana

v1.6.0

Compare Source

  • Switched to Github actions #​324 petergoldstein
  • Fixed misspelled method name in HTML reporter (percent_skipps -> percent_skips) #​326 contributed by andyw8
  • Removed deprecated call to Object#=~ #​318 contributed by etiennebarrie
  • Added option print_failure_summary to SpecReporter which causes failures and errors to print at the end of the test suite instead of inline
    as they happen #​306 contributed by picandocodigo

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Jun 20, 2024
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Jun 20, 2024
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 20, 2024
@renovate-bot renovate-bot force-pushed the renovate/minitest-reporters-1.x branch from dfd0e8d to 7b3604b Compare July 9, 2024 23:36
@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Jul 9, 2024
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Jul 9, 2024
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants