chore(deps): update dependency six to v0.3.1 - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
six (source)	dev	patch	== 0.3.0 → == 0.3.1

---

Release Notes

typicalpixel/six (six)

v0.3.1

Compare Source

Log Level Ignores

This release adds :ignore_log_levels because there are situations where during testing, logs become actually uncoverable due to how Logger's macros work: Logger.info/2 (and debug, notice, …) check the configured level before evaluating their message and metadata. Most test suites run with config :logger, level: :warning to keep output quiet, which means an info/debug call short-circuits and its arguments are never executed at runtime. :cover then reports those lines as missed - even though no test could ever cover them, short of lowering the log level (and flooding test output) or writing unwanted capture_log assertions just to force evaluation.

This bites hardest with multi-line structured logging, where each metadata line is its own coverable expression.

At level: :warning

Logger.info("inserted",   # this line runs (the level check)
  a: record.a,            # 0 calls - never evaluated
  b: record.b             # 0 calls - never evaluated
)

Logger.error("failed",    # emits at :warning…
  c: record.a             # …so this stays covered
)

The info metadata lines are uncoverable by design; the error ones are fine.

What this does

• Adds an :ignore_log_levels config - a list of levels whose log calls are dropped from coverage. Defaults to [], so it's opt-in and existing projects are unchanged.
• Six.Ignore.Logs parses each source via the AST and nullifies the entire span of matching Logger.(...) and Logger.log(level, ...) calls, including multi-line metadata (using the closing-paren line, falling back to the deepest argument line
  for paren-less calls).

Usage

# config/test.exs
config :six, ignore_log_levels: [:info, :debug]

This results in info/debug calls being excluded from coverage while warning/error stay enforced.

Acknowledgments

Thank you to Julia Castro Miller (@​julia-castro) for identifying this, and helping with the new feature.

---

Configuration

📅 Schedule: (in timezone Europe/Rome)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact 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: mix.lock

Command failed: install-tool elixir v1.20.1