build(deps): bump simplecov from 0.20.0 to 0.21.2 in /Library/Homebrew

[dependabot]

Bumps simplecov from 0.20.0 to 0.21.2.

Release notes

Sourced from simplecov's releases.

v0.21.2

Bugfixes

• maximum_coverage_drop won't fail any more if .last_run.json is still in the old format. Thanks @petertellgren
• maximum_coverage_drop won't fail if an expectation is specified for a previous unrecorded criterion, it will just pass (there's nothing, so nothing to drop)
• fixed bug in maximum_coverage_drop calculation that could falsely report it had dropped for minimal differences

v0.21.1

Bugfixes

• minimum_coverage_by_file works again as expected (errored out before 😱)

v0.21.0

The "Collate++" release making it more viable for big CI setups by limiting memory consumption. Also includes some nice new additions for branch coverage settings.

Enhancements

• Performance of SimpleCov.collate improved - it should both run faster and consume much less memory esp. when run with many files (memory consumption should not increase with number of files any more)
• Can now define the minimum_coverage_by_file, maximum_coverage_drop and refuse_coverage_drop by branch as well as line coverage. Thanks to @jemmaissroff
• Can set primary coverage to something other than line by setting primary_coverage :branch in SimpleCov Configuration. Thanks to @jemmaissroff

Misc

• reduce gem size by splitting Changelog into Changelog.md and a pre 0.18 Changelog.old.md, the latter of which is not included in the gem
• The interface of ResultMeger.merge_and_store is changed to support the collate performance improvements mentioned above. It's not considered an official API, hence this is not in the breaking section. For people using it to merge results from different machines, it's recommended to migrate to collate.

Changelog

Sourced from simplecov's changelog.

0.21.2 (2021-01-09)

Bugfixes

• maximum_coverage_drop won't fail any more if .last_run.json is still in the old format. Thanks @petertellgren
• maximum_coverage_drop won't fail if an expectation is specified for a previous unrecorded criterion, it will just pass (there's nothing, so nothing to drop)
• fixed bug in maximum_coverage_drop calculation that could falsely report it had dropped for minimal differences

0.21.1 (2021-01-04)

Bugfixes

• minimum_coverage_by_file works again as expected (errored out before 😱)

0.21.0 (2021-01-03)

The "Collate++" release making it more viable for big CI setups by limiting memory consumption. Also includes some nice new additions for branch coverage settings.

Enhancements

• Performance of SimpleCov.collate improved - it should both run faster and consume much less memory esp. when run with many files (memory consumption should not increase with number of files any more)
• Can now define the minimum_coverage_by_file, maximum_coverage_drop and refuse_coverage_drop by branch as well as line coverage. Thanks to @jemmaissroff
• Can set primary coverage to something other than line by setting primary_coverage :branch in SimpleCov Configuration. Thanks to @jemmaissroff

Misc

• reduce gem size by splitting Changelog into Changelog.md and a pre 0.18 Changelog.old.md, the latter of which is not included in the gem
• The interface of ResultMeger.merge_and_store is changed to support the collate performance improvements mentioned above. It's not considered an official API, hence this is not in the breaking section. For people using it to merge results from different machines, it's recommended to migrate to collate.

Commits

• a003140 prep 0.21.2 release
• 52cb560 More exit code check specs
• d4ed992 More thorough maximum coverage drop specs + fixes
• e0c5fd1 reformat and reformulate some cukes
• 10c1dff Bugfix maximum coverage drop with old .last_run file
• 120d0ea Fix minimum_coverage_by_file check & prep 0.21.1 (#966)
• 20af434 Release prep for 0.21.0 (#963)
• b95ce9a Enable and fix new cops
• 9cdc07b Upgrade rubocop and fix offenses
• 168f244 highlight why we can do result.to_hash.first
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

[MikeMcQuaid]

@dependabot recreate