Bump fasterer from 0.4.1 to 0.8.3

[dependabot-preview]

Bumps fasterer from 0.4.1 to 0.8.3.

Changelog

Sourced from fasterer's changelog.

0.8.3

• Merged in #79, a PR that makes sure the output is green when there are no failures.

0.8.2

• Fixes #77. An error occurs on the symbol to proc check when somebody invokes a method with no arguments on an array or range inside of the inspected block. Seems like a bug in the inspected code, but nevertheless it is a code path we need to support.

0.8.1

• Ignore lambda literals when checking symbol to proc. Thanks to kiyot for his fix in PR #74.

0.8.0

• Dropped support for ruby versions below 2.2.0 and locks ruby_parser to be above or equal to 1.14.1. The new ruby_parser version 1.14.1 explicitly requires ruby versions above 2.2.0, so this affects fasterer as well.

0.7.1

• Fix check_symbol_to_proc rule from crashing when there is no receiver #67

0.7.0

• More inclusive check_symbol_to_proc rule - don't only look at #each but any method that could leverage the symbol to proc rule. Merged through #41

0.6.0

• Enable placing the .fasterer.yml file not just in the current dir, but in any parent directory as well.

0.5.1

• Upgrade to ruby_parser 3.13.0 that fully supports Ruby 2.6

0.5.0

• New style of outputting offenses: spec/support/output/sample_code.rb:1 For loop is slower than using each.

Commits

• aa13bda Bump to version 0.8.3
• f634b8f Merge pull request #79 from Volosh1n/zero-offenses-green
• e53437b Merge pull request #80 from vk26/fix/update-readme-add-reviewdog
• 97d6ed4 Add action-fasterer to integration list in Readme
• 0fb6a17 Add missing question mark
• 1c6dc05 Make output fully green if there are no offenses
• aebf173 Update rake due to CVE-2020-8130
• 3cfe5f9 Bump to version 0.8.2
• 1a66130 Fix symbol to proc offense detector when a method is invoked on a range or array
• 7a6d4d4 For readability replace unless with if
• 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
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[codecov-io]

Codecov Report

Merging #599 into master will not change coverage by %.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #599   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          399       399           
  Lines        10675     10675           
=========================================
  Hits         10675     10675           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update adfe0b6...dc11bfa. Read the comment docs.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (master@adfe0b6). Learn more about missing BASE report.

Additional details and impacted files

@@            Coverage Diff             @@
##             master      #599   +/-   ##
==========================================
  Coverage          ?   100.00%           
==========================================
  Files             ?       399           
  Lines             ?     10675           
  Branches          ?         0           
==========================================
  Hits              ?     10675           
  Misses            ?         0           
  Partials          ?         0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.