Skip to content

build(deps): update elixir dependencies (non-major)#1840

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/elixir-dependencies-(non-major)
Open

build(deps): update elixir dependencies (non-major)#1840
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/elixir-dependencies-(non-major)

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2026

This PR contains the following updates:

Package Type Update Change Pending
credo (source) dev patch 1.7.151.7.16 1.7.17
csv (source) prod patch 3.2.13.2.2
dialyxir (source) dev patch 1.4.21.4.7
ex_doc (source) dev patch 0.40.00.40.1
ex_doc (source) dev minor ~> 0.29~> 0.40
excoveralls (source) dev minor ~> 0.15~> 0.18
guardian (source) prod minor 2.3.22.4.0
guardian (source) prod minor ~> 2.3.2~> 2.4.0
horde (source) prod minor ~> 0.9~> 0.10
mimic (source) dev minor ~> 1.7.4~> 1.12.0
observer_cli (source) prod minor 1.7.41.8.6
observer_cli (source) prod minor 1.6.11.8.6
phoenix (source) prod minor 1.7.21.8.4 1.8.5
phoenix (source) prod patch 1.8.31.8.4 1.8.5
phoenix_ecto (source) prod minor 4.2.14.7.0
phoenix_view (source) prod patch 2.0.22.0.4
plug_cowboy (source) prod minor 2.7.52.8.0
plug_cowboy (source) prod minor 2.6.12.8.0
pretty_log (source) prod minor ~> 0.1.0~> 0.9.0

Release Notes

rrrene/credo (credo)

v1.7.16

Compare Source

  • 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
beatrichartz/csv (csv)

v3.2.2

Compare Source

jeremyjh/dialyxir (dialyxir)

v1.4.7

Compare Source

v1.4.6

Compare Source

Fixed
  • CallWithoutOpaque function clause error on OTP-28
  • invalid_contract warning showed spec twice instead of success typing
Changed
  • Update ex_doc to the latest version for an improved UI
Docs
  • Add a note about the :unknown flag to the "Default Flags" section in the README
  • Fix dead hex doc links by including CI config docs in mix.exs's :docs
  • Fix a typo in the README
CI
  • Update the Ubuntu version used in CI to 24.04

v1.4.5

Compare Source

Fixed
  • Crash when default ignore file missing and custom file specified
  • Revert format option ignore_file_string to ignore_file_strict

v1.4.4

Compare Source

Fixed
  • Invalid contract formatting failed on OTP 26 & later.
  • Empty ignore files are ignored.
  • Several improvements and corrections to documentation.
Changed
  • Updated Erlex minimum version to 0.27, bringing in several fixes and improvements.
Added
  • Multiple formatters can be used in the same invocation.

v1.4.3

Compare Source

Fixed
  • Warnings with line & column.
  • Formatting of :record_match warning.
elixir-lang/ex_doc (ex_doc)

v0.40.1

Compare Source

  • Enhancements
    • Remove link to source from generated .md files

    • Improve word-breaking of module names and sizing of main page titles

    • Include description in llms.txt

    • Bug fixes

      • Fix headers in custom groups
parroty/excoveralls (excoveralls)

v0.18.5

Compare Source

Changes
  • Fix Json output name when export isn't set (#​337)

v0.18.4

Compare Source

Enhancements
  • Add Custom Filename support for coveralls.json (#​335)
Changes
  • Elixir 1.18 compatibility (#​333)

v0.18.3

Compare Source

Changes
  • Avoid warning messages for Cobertura
    • Update Range to use function syntax (#​332)

v0.18.2

Compare Source

Enhancements
  • Print warnings about incorrectly used ignore-markers (#​325), such as start-marker
    without a corresponding stop-marker, or two start-markers without a stop-marker in-between etc.
Changes
  • Fix Elixir 1.17 single-quoted string warning (#​327)

v0.18.1

Compare Source

Changes
  • Use explicit steps to remove 1.16 deprecation warning in Cobertura (#​322).

v0.18.0

Compare Source

Changes

v0.17.1

Compare Source

Enhancements
  • Accept custom http options (#​319).

v0.17.0

Compare Source

Changes
  • Replace hackney with httpc (#​311).
  • Update Elixir requirement to 1.11+ (#​316).
  • Fix lcov 2.0 source file handling (#​315).
  • Import .coverdata after test run and improve documentation (#​309).
    • Fixes around --import-cover option.

v0.16.1

Compare Source

Changes
  • Cobertura now handles defprotocol and defimpl definitions (#​306).

v0.16.0

Compare Source

Enhancements
  • Add coveralls.multiple command (#​303).
  • Support # coveralls-ignore-next-line comment for ignoring single next line.
    • Ignore single next line (#​301).
  • Add mix coveralls.cobertura task.

v0.15.3

Compare Source

Enhancements
  • Support --import_cover option.
    • Import coverdata if needed (#​292).

v0.15.2

Compare Source

Changes
  • Add .coverdata file export (#​298).
    • Allow default use of mix test --cover --export-coverage XXX.

v0.15.1

Compare Source

Changes
  • Improve logging for a case with the missing source file (#​295).
ueberauth/guardian (guardian)

v2.4.0

Compare Source

  • Add compatibility with Elixir 1.18.0
derekkraan/horde (horde)

v0.10.0

  • Added optional TTL to Horde.DynamicSupervisor's :proxy_operation messages. The Time-to-Live defaults to :infinity for full backwards compatibility. This TTL helps prevent potential issues where messages could loop forever between a set of nodes which disagree on which node should execute the task.
  • [BREAKING] Horde.DynamicSupervisor's new :proxy_message_ttl option configures the maximum TTL for proxy messages. It takes an integer denoting the maximum number of hops a message can travel, or the atom :infinity (default). This can be a breaking change: when upgrading do not set this option to an integer. You can explicity set it to :infinity or leave it default. If this is set to an integer, upgraded nodes won't be able to proxy to non-upgrade nodes.
edgurgel/mimic (mimic)

v1.12.0: Mimic 1.12.0

Compare Source

What's Changed

New Contributors

Full Changelog: edgurgel/mimic@v1.11.2...v1.12.0

v1.11.2: Mimic 1.11.2

Compare Source

What's Changed

Full Changelog: edgurgel/mimic@v1.11.1...v1.11.2

v1.11.1: Mimic 1.11.1

Compare Source

What's Changed

New Contributors

Full Changelog: edgurgel/mimic@v1.11.0...v1.11.1

v1.11.0: Mimic 1.11.0

Compare Source

What's Changed

New Contributors

Full Changelog: edgurgel/mimic@v1.10.2...v1.11.0

v1.10.2: Mimic 1.10.2

Compare Source

What's Changed

New Contributors

Full Changelog: edgurgel/mimic@v1.10.1...v1.10.2

v1.10.1: Mimic 1.10.1

Compare Source

What's Changed

New Contributors

Full Changelog: edgurgel/mimic@v1.10.0...v1.10.1

v1.10.0: Mimic 1.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: edgurgel/mimic@v1.9.0...v1.10.0

Experimental type checking for copied modules

One can pass type_check: true when a module is copied to also get the function expected/stubbed to
validate the arguments and return value using Ham which is essentially
what Hammox improved on Mox.

Mimic.copy(:cowboy_req, type_check: true)

If there is any problem with the arguments or return values of the stubbed functions on your tests you might see
an error like this one:

     ** (Mimic.TypeCheckError) :cowboy_req.parse_qs/1: 1st argument value %{} does not match 1st parameter's type :cowboy_req.req().
       Could not find a map entry matching required(:method) => binary().

This feature is experimental at the moment which means that it might change a little bit how this
is configured and used. Feedback is welcome!

v1.9.0: Mimic 1.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: edgurgel/mimic@v1.8.2...v1.9.0

v1.8.2: Mimic 1.8.2

Compare Source

Fix cover error when JIT is enabled. Issue #​70

Full Changelog: edgurgel/mimic@v1.8.1...v1.8.2

v1.8.1: Mimic 1.8.1

Compare Source

  • Fix Mimic copying for erlang modules

v1.8.0: Mimic 1.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: edgurgel/mimic@v1.7.4...v1.8.0

zhongwencool/observer_cli (observer_cli)

v1.8.6: Coverage 92%

Compare Source

What's Changed

New Contributors

Full Changelog: zhongwencool/observer_cli@1.8.5...1.8.6

v1.8.5

Compare Source

What's Changed

Full Changelog: zhongwencool/observer_cli@1.8.4...1.8.5

v1.8.4

Compare Source

What's Changed
New Contributors

Full Changelog: zhongwencool/observer_cli@1.8.3...1.8.4

v1.8.3

Compare Source

What's Changed
New Contributors

Full Changelog: zhongwencool/observer_cli@v1.8.2...1.8.3

v1.8.2

Compare Source

What's Changed
New Contributors

Full Changelog: zhongwencool/observer_cli@1.8.1...v1.8.2

v1.8.1

Compare Source

What's Changed

Full Changelog: zhongwencool/observer_cli@1.8.0...1.8.1

v1.8.0: Show process's label and node's dist_stats

Compare Source

New Feature:
  • Process Label Display: Now shows the process's label when set using proc_lib:set_label(Label).
  • System View Update: Displays the number of bytes in the output distribution queue, which sits between Erlang code and the port driver, using the undocumented function erlang:dist_get_stat/1.
  • Added support for to jump to a specific process PID.
Bug Fix
  • Resolved an issue where the Doc View would not display when the OTP version is 27.
iShot_2024-10-21_17 15 49 iShot_2024-10-21_17 13 10 iShot_2024-10-21_17 13 41

v1.7.5

Compare Source

What's Changed
New Contributors

Full Changelog: zhongwencool/observer_cli@1.7.4...1.7.5

phoenixframework/phoenix (phoenix)

v1.8.4

Compare Source

JavaScript Client Bug Fixes
  • Fix bug reconnecting connections when close was gracefully initiated by server
  • Fix LongPoll transport name in sessionStorage and logs
Enhancements
  • Adds guards support in assert_push, assert_broadcast, and assert_reply
  • Enable purging in Phoenix code server for Elixir 1.20

v1.8.3

Compare Source

Enhancements
  • Add top-level phoenix config: sort_verified_routes_query_params to enable sorting query params in verified routes during tests
Bug fixes
  • Fix endpoint port config in an umbrella application. (#​6549)
  • Drop incoming channel messages with stale join refs

v1.8.2

Compare Source

Bug fixes
  • [phoenix.js] fix issue where LongPoll can cause "unmatched topic" errors (observed on iOS only) (#​6538)
  • [phx.gen.live] fix tests when schema and table names are equal (#​6477)
  • [Verified Routes] do not add path prefixes for static routes
  • [Phoenix.Endpoint] fix LongPoll being active by default since 1.8.0 (#​6487)
Enhancements
  • [phoenix.js] socket now stops reconnection attempts while the page is hidden (#​6534)
  • [phx.new] (re-)add <.input field={@&#8203;form[:foo]} type="hidden" /> support in core components
  • [phx.new] set force_ssl in prod.exs by default (#​6435)
  • [phx.new] change --docker base image to debian trixie (#​6521)
  • [Phoenix.Socket.assign/2] allow passing a function as second argument assign(socket, fn _existing_assigns -> %{this_gets: "merged"} end) (#​6530)
  • [Phoenix.Controller.assign/2] allow passing a function as second argument (#​6542)
  • [Phoenix.Controller.assign/2] support keyword lists and maps as second argument similar to LiveView (#​6513)
  • [Presence] support custom dispatcher for presence_diff broadcast (#​6500)
  • [AGENTS.md] add short test guidelines to usage rules

v1.8.1

Compare Source

Bug fixes
  • [phx.new] Fix AGENTS.md failing to include CSS and JavaScript sections

v1.8.0

Compare Source

Bug fixes
  • [phx.new] Don't include node_modules override in generated tsconfig.json
Enhancements
  • [phx.gen.live|html|json] - Make context argument optional. Defaults to the plural name.
  • [phx.new] Add mix precommit alias
  • [phx.new] Add AGENTS.md generation compatible with usage_rules
  • [phx.new] Add usage_rules folder to installer, allowing to sync generic Phoenix rules into new projects
  • [phx.new] Use LiveView 1.1 release in generated code
  • [phx.new] Ensure theme selector and flash closing works without LiveView

v1.7.21

Compare Source

v1.7.20

Compare Source

v1.7.19

Compare Source

v1.7.18

Compare Source

v1.7.17

Compare Source

v1.7.16

Compare Source

v1.7.15

Compare Source

v1.7.14

Compare Source

v1.7.13

Compare Source

v1.7.12

Compare Source

v1.7.11

Compare Source

v1.7.10

Compare Source

v1.7.9

Compare Source

v1.7.8

Compare Source

v1.7.7

Compare Source

v1.7.6

Compare Source

v1.7.5

Compare Source

v1.7.4

Compare Source

v1.7.3

Compare Source

phoenixframework/phoenix_ecto (phoenix_ecto)

v4.7.0

Compare Source

v4.6.6

Compare Source

  • Bug fixes
    • Keep backwards compatibility on sandbox API

v4.6.5

  • Bug fixes
    • Unallow existing allowances when attempting to allow a Plug to access a connection

v4.6.4

  • Enhancements
    • Wrap raised Ecto exceptions so context is not lost
    • Do not override changeset actions

v4.6.3

Compare Source

  • Enhancements

    • Add prefix option to check repo status plug
  • Bug fix

    • Fix map.field notation warning on Elixir 1.17

v4.6.2

Compare Source

  • Bug fix
    • Attach directories to Pending Migrations exception

v4.6.1

Compare Source

  • Bug fix
    • Ensure "Create database" action is shown when database is not available

v4.6.0

Compare Source

  • Enhancements
    • Return 400 for character encoding errors in Postgrex
    • Bump Elixir requirement to v1.11+

v4.5.1

Compare Source

  • Bug fix
    • Fix a regression on nested inputs_for

v4.5.0

Compare Source

  • Enhancements
    • Support Phoenix.HTML ~> 4.1
    • Use to_form's :action as changeset action when passed

v4.4.3

Compare Source

  • Enhancements
    • Support Phoenix.HTML ~> 4.0

v4.4.2

Compare Source

  • Enhancements
    • Fix warning on undefined migration function when ecto_sql is missing
    • Support changesets with 3-arity cast function

v4.4.1

Compare Source

  • Enhancements
    • Allow migration_lock to be specified in check_repo_status
    • Support multiple repos on sandbox plug API
    • Support configuring multiple custom migration paths

v4.4.0

Compare Source

This release bumps the requirement for Ecto and Phoenix.

  • Enhancements
    • Trap exits when activating the test sandbox

v4.3.0

Compare Source

  • Enhancements
    • Support :phoenix_html v3.0
phoenixframework/phoenix_view (phoenix_view)

v2.0.4

  • Fix warning when using elixir v1.17

v2.0.3

Compare Source

  • Relax Phoenix.HTML dependency
elixir-plug/plug_cowboy (plug_cowboy)

v2.8.0

Compare Source

Enhancements
  • Remove supported for deprecated next_protocols_advertised
ispirata/pretty_log (pretty_log)

v0.9.0

Compare Source


Configuration

📅 Schedule: Branch creation - "before 6am on Monday" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Pull requests that update a dependency file elixir automerge labels Mar 5, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Mar 5, 2026

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: apps/astarte_realm_management/mix.exs
Artifact update for credo resolved to version 1.7.17, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.7.16
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: libs/astarte_data_access/mix.exs
Artifact update for credo resolved to version 1.7.17, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.7.16
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: apps/astarte_data_updater_plant/mix.exs
Artifact update for credo resolved to version 1.7.17, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.7.16
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: apps/astarte_trigger_engine/mix.exs
Artifact update for credo resolved to version 1.7.17, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.7.16
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: libs/astarte_events/mix.exs
Artifact update for credo resolved to version 1.7.17, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.7.16
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: libs/astarte_generators/mix.exs
Artifact update for credo resolved to version 1.7.17, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.7.16
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: libs/astarte_rpc/mix.exs
Artifact update for credo resolved to version 1.7.17, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.7.16
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

@github-actions github-actions bot added the size/m label Mar 5, 2026
@codecov
Copy link

codecov bot commented Mar 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.92%. Comparing base (c98b9ad) to head (95eb639).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1840      +/-   ##
==========================================
- Coverage   85.96%   85.92%   -0.05%     
==========================================
  Files         559      559              
  Lines        9757     9757              
==========================================
- Hits         8388     8384       -4     
- Misses       1369     1373       +4     

see 5 files with indirect coverage changes

Flag Coverage Δ
astarte_appengine_api 85.76% <ø> (-0.11%) ⬇️
astarte_data_access 82.55% <ø> (ø)
astarte_data_updater_plant 86.98% <ø> (-0.08%) ⬇️
astarte_events 79.40% <ø> (ø)
astarte_generators 97.39% <ø> (-0.35%) ⬇️
astarte_housekeeping 81.93% <ø> (+0.14%) ⬆️
astarte_pairing 84.83% <ø> (ø)
astarte_realm_management 87.66% <ø> (ø)
astarte_rpc 88.23% <ø> (ø)
astarte_trigger_engine 82.47% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge dependencies Pull requests that update a dependency file elixir size/m

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants