Skip to content

Bump credo from 1.7.12 to 1.7.18#25

Merged
joladev merged 2 commits into
mainfrom
dependabot/hex/credo-1.7.18
May 9, 2026
Merged

Bump credo from 1.7.12 to 1.7.18#25
joladev merged 2 commits into
mainfrom
dependabot/hex/credo-1.7.18

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 6, 2026 •
edited
Loading

Bumps credo from 1.7.12 to 1.7.18.

Release notes

Sourced from credo's releases.

v1.7.18

Check it out on Hex: https://hex.pm/packages/credo/1.7.18

  • Fix compatibility & compiler warnings with Elixir 1.20.0-rc.4
  • Fix problem with transitive deps in umbrella apps
  • Credo.Check.Warning.UnusedMapOperation fix false positives

v1.7.17

Check it out on Hex: https://hex.pm/packages/credo/1.7.17

  • Credo.Check.Readability.ModuleDoc add new param :ignore_modules_using (defaults to [Credo.Check, Ecto.Schema, Phoenix.LiveView, ~r/\.Web$/])
  • Credo.Check.Warning.UnusedOperation update :modules param: instead of a list of functions to check, :all can be given to check all functions in a module
  • New Check: Credo.Check.Refactor.CondInsteadOfIfElse
  • New Check: Credo.Check.Warning.WrongTestFilename

v1.7.16

Check it out on Hex: https://hex.pm/packages/credo/1.7.16

  • Fix compatibility & compiler warnings with Elixir 1.20.0-rc.1
  • Credo.Check.Refactor.PassAsyncInTestCases add new param :force_comment_on_explicit_false (defaults to false)
  • Credo.Check.Warning.Dbg add new param :allow_captures (defaults to false)
  • New Check: Credo.Check.Warning.UnusedMapOperation
  • New Check: Credo.Check.Warning.UnusedOperation

v1.7.15

Check it out on Hex: https://hex.pm/packages/credo/1.7.15

  • Improve performance on large projects
  • Parse token_metadata for source files
  • Credo.Check.Warning.ExpensiveEmptyEnumCheck have better issue messages
  • Credo.Check.Refactor.MatchInCondition add new param :allow_operators
  • Credo.Check.Refactor.MatchInCondition fix false positive
  • Credo.Check.Readability.AliasOrder fix false positive
  • Credo.Check.Readability.FunctionNames fix false positive
  • Credo.Check.Readability.SinglePipe add new param :allow_blocks (defaults to true)
  • Credo.Check.Refactor.ModuleDependencies fix false positive

v1.7.14

Check it out on Hex: https://hex.pm/packages/credo/1.7.14

  • Fixed regression for DuplicatedCode
  • Expanded Credo.Check.Warning.ExpensiveEmptyEnumCheck to cover less obvious cases
  • New Check: Credo.Check.Warning.StructFieldAmount

1.7.13

Check it out on Hex: https://hex.pm/packages/credo/1.7.13

  • Fix compatibility & compiler warnings with Elixir 1.19
  • Credo.Check.Refactor.ABCSize fixed false positive
Changelog

Sourced from credo's changelog.

1.7.18

  • Fix compatibility & compiler warnings with Elixir 1.20.0-rc.4
  • Fix problem with transitive deps in umbrella apps
  • Credo.Check.Warning.UnusedMapOperation fix false positives

1.7.17

  • Credo.Check.Readability.ModuleDoc add new param :ignore_modules_using (defaults to [Credo.Check, Ecto.Schema, Phoenix.LiveView, ~r/\.Web$/])
  • Credo.Check.Warning.UnusedOperation update :modules param: instead of a list of functions to check, :all can be given to check all functions in a module
  • New Check: Credo.Check.Refactor.CondInsteadOfIfElse
  • New Check: Credo.Check.Warning.WrongTestFilename

1.7.16

  • Fix compatibility & compiler warnings with Elixir 1.20.0-rc.1
  • Credo.Check.Refactor.PassAsyncInTestCases add new param :force_comment_on_explicit_false (defaults to false)
  • Credo.Check.Warning.Dbg add new param :allow_captures (defaults to false)
  • New Check: Credo.Check.Warning.UnusedMapOperation
  • New Check: Credo.Check.Warning.UnusedOperation

1.7.15

  • Improve performance on large projects
  • Parse token_metadata for source files
  • Credo.Check.Warning.ExpensiveEmptyEnumCheck have better issue messages
  • Credo.Check.Refactor.MatchInCondition add new param :allow_operators
  • Credo.Check.Refactor.MatchInCondition fix false positive
  • Credo.Check.Readability.AliasOrder fix false positive
  • Credo.Check.Readability.FunctionNames fix false positive
  • Credo.Check.Readability.SinglePipe add new param :allow_blocks (defaults to true)
  • Credo.Check.Refactor.ModuleDependencies fix false positive

1.7.14

  • Fix regression for DuplicatedCode
  • Expand Credo.Check.Warning.ExpensiveEmptyEnumCheck to cover less obvious cases
  • New Check: Credo.Check.Warning.StructFieldAmount

1.7.13

  • Fix compatibility & compiler warnings with Elixir 1.19
  • Credo.Check.Refactor.ABCSize fixed false positive
Commits
  • 63d9bf4 Bump version to 1.7.18
  • e5f7956 Update CHANGELOG
  • da4f401 Fix false positives for UnusedMapOperation
  • 288a1b1 Update Elixir to 1.20.0-rc.4
  • 474b769 Fix errors due to new token format
  • a03f6bd Fix error raised by new sigil token format
  • aea4b77 Fix compiler warnings for 1.20.0-rc.2
  • 1169b69 Add requirements "loadpaths" to Mix task.
  • f0d654f Add experimental JSONL output to suggest command
  • 068fcc7 Bump version to 1.7.17
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file elixir Pull requests that update elixir code labels May 6, 2026
@control-devstats-io
Copy link
Copy Markdown

control-devstats-io Bot commented May 6, 2026

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

  • User: dependabot[bot]
  • Repository: jola.dev
  • Permission Level: none
  • Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.

This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

  • Executing malicious code on the deployment server
  • Accessing environment variables and secrets
  • Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

4 similar comments
@control-devstats-io
Copy link
Copy Markdown

control-devstats-io Bot commented May 6, 2026

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

  • User: dependabot[bot]
  • Repository: jola.dev
  • Permission Level: none
  • Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.

This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

  • Executing malicious code on the deployment server
  • Accessing environment variables and secrets
  • Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

@control-devstats-io
Copy link
Copy Markdown

control-devstats-io Bot commented May 6, 2026

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

  • User: dependabot[bot]
  • Repository: jola.dev
  • Permission Level: none
  • Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.

This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

  • Executing malicious code on the deployment server
  • Accessing environment variables and secrets
  • Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

@control-devstats-io
Copy link
Copy Markdown

control-devstats-io Bot commented May 6, 2026

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

  • User: dependabot[bot]
  • Repository: jola.dev
  • Permission Level: none
  • Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.

This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

  • Executing malicious code on the deployment server
  • Accessing environment variables and secrets
  • Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

@control-devstats-io
Copy link
Copy Markdown

control-devstats-io Bot commented May 6, 2026

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

  • User: dependabot[bot]
  • Repository: jola.dev
  • Permission Level: none
  • Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.

This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

  • Executing malicious code on the deployment server
  • Accessing environment variables and secrets
  • Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

@dependabot dependabot Bot force-pushed the dependabot/hex/credo-1.7.18 branch 2 times, most recently from 8ac27e9 to 3737ff6 Compare May 9, 2026 14:14
dependabot Bot and others added 2 commits May 9, 2026 15:31
@dependabot @joladev
Bump credo from 1.7.12 to 1.7.18
7248856 
Bumps [credo](https://github.com/rrrene/credo) from 1.7.12 to 1.7.18.
- [Release notes](https://github.com/rrrene/credo/releases)
- [Changelog](https://github.com/rrrene/credo/blob/master/CHANGELOG.md)
- [Commits](rrrene/credo@v1.7.12...v1.7.18)

---
updated-dependencies:
- dependency-name: credo
  dependency-version: 1.7.18
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@joladev
fix
3b7a8fc
@joladev joladev force-pushed the dependabot/hex/credo-1.7.18 branch from 3737ff6 to 3b7a8fc Compare May 9, 2026 21:34
@joladev joladev merged commit 5e574f2 into main May 9, 2026
1 check passed
@joladev joladev deleted the dependabot/hex/credo-1.7.18 branch May 9, 2026 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file elixir Pull requests that update elixir code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@joladev