Bump credo from 1.5.6 to 1.6.0

[dependabot[bot]]

Bumps credo from 1.5.6 to 1.6.0.

Changelog

Sourced from credo's changelog.

1.6.0

• Credo changes from supporting the last 5 minor Elixir versions to the last 6, to be compatible with Elixir's own support policy regarding bug fixes and security patches
• Credo's docs now provide the ability to link specific check params, e.g. check out :max_length for MaxLineLength
• Credo.Check.Readability.SinglePipe now supports :allow_0_arity_functions
• Credo.Check.Design.AliasUsage now supports :only
• Credo now fails with an error message if a plugin module can not be initialized
• Prepare compatibility with Elixir 1.13

First Run Mode

Credo 1.6 features a new mode, designed to be run every time you introduce Credo to an existing codebase.

mix credo --first-run

This offers a couple of suggestions on how to introduce Credo to your workflow/CI.

All of these suggestions are contextualized and project-specific, here's an example when running it on Credo's codebase:

-------------------------------------- 8< --------------------------------------
Where to start?
That's a lot of issues to deal with at once.
While not recommended, you could simply start ignoring issues for the time being:
mix credo --ignore readability      # exclude checks matching a given phrase

You can use diff to only show the issues that were introduced on this branch:
mix credo diff master

Compare to a point in history
Alternatively, you can use diff to only show the issues that were introduced after
a certain tag or commit:
mix credo diff v1.5.6               # use the latest tag

mix credo diff e0d84ba9             # use the current HEAD of master

Lastly, you can compare your working dir against this point in time:
mix credo diff --since 2021-08-28   # use the current date

</tr></table>

... (truncated)

Commits

• fdf7b41 Bump version to 1.6.0
• 401c14d Update CHANGELOG
• 71a7b24 Merge pull request #906 from v0idpwn/fix/elixir-1-13-tokenizer
• fb593b4 Merge pull request #899 from lesha1201/fix/failing-tests
• b449265 Support elixir 1.13 tokenizer results
• 10b8c1f Merge pull request #904 from J3RN/multi-alias-verbiage
• b876934 Merge pull request #897 from hrzndhrn/fix-apply
• 2966693 One further fix
• 913d0da Clarify verbiage for Readability.MultiAlias check
• abf96da Revert formatting
• 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)