Skip to content

build(deps-dev): bump the dev group across 1 directory with 3 updates - #180

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/dev-4561d91d2b
Closed

build(deps-dev): bump the dev group across 1 directory with 3 updates#180
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/dev-4561d91d2b

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 25, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the dev group with 3 updates in the / directory: complexipy, ruff and pytest-mock.

Updates complexipy from 8.0.1 to 8.1.0

Release notes

Sourced from complexipy's releases.

8.1.0

Minor release: complexipy now ships a language server. complexipy lsp gives any editor with an LSP client inlay hints, hover, and warnings, and the VS Code extension and a new Zed extension run on top of it. The CLI gains --fix for machine-applicable suggestions and --select/--ignore for rule selection, Python 3.15 syntax parses, and a JSON schema describes the configuration.

Added

  • A language server: complexipy lsp speaks the Language Server Protocol on stdio, so any editor with an LSP client gets complexity feedback with no per-editor code. It answers inlay hint requests with the cognitive complexity of each function and, optionally, the increment contributed by each line; it answers hover requests with the function total, its threshold status, and the top refactoring suggestion, built on demand for the hovered function so large files stay responsive; and it publishes a warning for every function above max-complexity-allowed. Diagnostics respect inline ignore comments, so the editor and the CLI agree. The per-function hint sits at the end of the line that closes the declaration, so a wrapped signature keeps the hint on its closing line, and a document that does not parse keeps the last parsed hints plus one complexipy-parse-error warning, placed where the parser fails, until it parses again. Configuration problems, such as an unknown rule id in select, appear in the editor as a warning message (#272). The server reloads the configuration when a configuration file at a folder root changes, in editors that watch files for it (#257). A Zed extension in zed/ starts the server in Zed, and the inlay hints carry a left padding so they do not touch the code (#255). See Editor Integration for the VS Code, Neovim, and Zed setup.

  • The VS Code extension is now a client of the language server and drops its bundled WASM engine (#253). Results update while you type, with no save (#133), and hints and warnings follow max-complexity-allowed and the [tool.complexipy.lsp] settings (#127). The extension needs the complexipy command, and a complexipy.server.path setting points it at a specific binary.

  • The VS Code extension is published to OpenVSX as well as the Visual Studio Marketplace, so VSCodium and other VS Code forks can install it (#145). A vscode-v* tag publishes the same VSIX to both registries.

  • A [tool.complexipy.lsp] configuration section, with inlay-hints (threshold, always, or never), per-line-hints, and diagnostics. Hints are gated on max-complexity-allowed by default, so a project that sets no options sees feedback only where it matters.

  • complexipy-core gains a config feature that owns configuration file discovery, so the CLI and the server read complexipy.toml, .complexipy.toml, and pyproject.toml through one code path.

  • The server applies exclude one pattern at a time: a malformed pattern is reported once per configuration load and skipped while the remaining patterns keep applying, and a list too large to compile as one program is reported once and still applied. A CLI run stops on either.

  • Each workspace folder reads its own configuration (#273). In a workspace with several folders, a document uses the threshold, rule selection, exclude patterns, and [tool.complexipy.lsp] settings of the deepest folder that contains it, and a document outside every folder uses the first folder. The server declares workspace folder support, so folders that the editor adds or removes take effect without a restart.

  • Per-rule suppression and rule selection (#208). --select and --ignore (repeatable and comma-separated) pick the active refactoring rules, and ignore wins on conflict. complexipy.toml, .complexipy.toml, and pyproject.toml take matching select and ignore keys, and a flag replaces the toml key it names. A toml value splits on commas like the flags, so select = "C007, C002" names two rules. An ignore comment accepts a bracketed rule list, # complexipy: ignore[C007], which suppresses only the named rules for one function, while a bare marker keeps suppressing the whole function. An inactive rule disappears from every output format and never consumes a slot of the per-function plan cap, so a hidden rule can never block a visible one. An unknown rule id warns on stderr that it matches no registered rule, and a second warning says so when select and ignore leave no rule active. Rule selection never changes the exit code.

  • --fix applies machine-applicable suggestions to the source files (#204). A suggestion is fixable when its tier is MachineApplicable and its replacement is a faithful splice (spliceable), which covers C002 (loop guards) and C007 (collapsible if); C005 is not spliceable and stays out. --fix changes only functions whose complexity is above max-complexity-allowed, and every pass checks the threshold again, so a function stops changing once it passes. Functions at or under the threshold keep their suggestions in the report and are never rewritten. One run fixes every analyzed file, bottom-to-top within each file, and prints a syntax-highlighted unified diff of the applied changes, with line numbers, one context line per hunk, and the rule that fired, plus a summary of fixed and skipped fixes that shows the reduction per fix. Every summary line carries the file's line numbers from before the run, and each skip reports once. The run repeats pass by pass, up to 8 passes, until no fixable plan remains, so a fix that exposes a new fixable plan is applied in a later pass; later passes label their diffs. Long diff rows truncate at the terminal width. When nothing is fixable the run prints No fixes to apply. --fix runs in any git state: uncommitted changes, untracked files, and a missing repository never block it, and no extra flag is needed. A fix keeps the file's line endings and its trailing newline. A fix that would produce invalid Python is reverted and reported, and the write is a parse-checked temp file renamed over the original with its permissions kept. The report and the gates measure the post-fix state, so re-analyzing a fixed file shows the finding gone and the exact measured reduction. --fix --dry-run prints only the diff and writes nothing. --select/--ignore decide which rules may fix.

  • Python 3.15 support (#265). Lazy imports (PEP 810) and unpacking in comprehensions (PEP 798) now parse in the CLI, the language server, the Python API, and the web build. A lazy import adds no complexity, and an unpacking comprehension scores like the plain one. Releases now publish CPython 3.15 wheels for Windows and macOS.

  • A JSON schema for the configuration (#270). complexipy.schema.json describes every key of complexipy.toml, .complexipy.toml, and [tool.complexipy], including [diff] and [lsp], so a TOML language server such as Taplo offers completion, hover text, and validation. The schema rejects unknown keys. complexipy itself still ignores them.

Changed

  • lsp is a reserved first argument: complexipy lsp starts the language server, so a file or directory with that name needs complexipy -- lsp to be analyzed. On a terminal the server prints that hint when both the reserved word and a path named lsp are present.
  • StringOrList moved from complexipy-cli::types to the new complexipy-core config module, and the CLI still re-exports it from its old path. Every workspace crate remains publish = false, so no published Rust API changes.
  • Added manylinux_2_31_riscv64 wheel builds for RISC-V support. The release matrix now separates the Rust toolchain triple (target) from the platform shorthand (arch), which keeps the existing wheel and artifact names unchanged. (#259)
  • RuleCategory, Applicability, and DiffStatus are real enum.Enum subclasses: they iterate, they carry .name and .value, and isinstance(x, enum.Enum) holds.
  • requires-python is now >=3.8,<3.16, so installers stop choosing complexipy on a Python version no release has built or tested. The bound rises when a release adds the next Python version. On Python 3.16 and later, pip falls back to 8.0.1, the last release without the bound. (#281)

Fixed

  • --color governs every styled line the CLI writes, on stdout and stderr. auto turns color off when the stream is not a terminal or NO_COLOR is set, no removes it from the report, the banner, and the warnings, and --plain output is never styled. In 8.0.1 the report carried ANSI codes on a pipe, under --color no, and under NO_COLOR.

PRs

... (truncated)

Changelog

Sourced from complexipy's changelog.

[8.1.0] - 2026-10-18

Added

  • A language server: complexipy lsp speaks the Language Server Protocol on stdio, so any editor with an LSP client gets complexity feedback with no per-editor code. It answers inlay hint requests with the cognitive complexity of each function and, optionally, the increment contributed by each line; it answers hover requests with the function total, its threshold status, and the top refactoring suggestion, built on demand for the hovered function so large files stay responsive; and it publishes a warning for every function above max-complexity-allowed. Diagnostics respect inline ignore comments, so the editor and the CLI agree. The per-function hint sits at the end of the line that closes the declaration, so a wrapped signature keeps the hint on its closing line, and a document that does not parse keeps the last parsed hints plus one complexipy-parse-error warning, placed where the parser fails, until it parses again. Configuration problems, such as an unknown rule id in select, appear in the editor as a warning message (#272). The server reloads the configuration when a configuration file at a folder root changes, in editors that watch files for it (#257). A Zed extension in zed/ starts the server in Zed, and the inlay hints carry a left padding so they do not touch the code (#255). See Editor Integration for the VS Code, Neovim, and Zed setup.

  • The VS Code extension is now a client of the language server and drops its bundled WASM engine (#253). Results update while you type, with no save (#133), and hints and warnings follow max-complexity-allowed and the [tool.complexipy.lsp] settings (#127). The extension needs the complexipy command, and a complexipy.server.path setting points it at a specific binary.

  • The VS Code extension is published to OpenVSX as well as the Visual Studio Marketplace, so VSCodium and other VS Code forks can install it (#145). A vscode-v* tag publishes the same VSIX to both registries.

  • A [tool.complexipy.lsp] configuration section, with inlay-hints (threshold, always, or never), per-line-hints, and diagnostics. Hints are gated on max-complexity-allowed by default, so a project that sets no options sees feedback only where it matters.

  • complexipy-core gains a config feature that owns configuration file

... (truncated)

Commits
  • cec85bd fix(tests): overflow the exclude program on 32-bit windows too
  • 446a902 fix(ci): give the windows test venv the setup-python interpreter path
  • f5ce56e docs(changelog): release 8.1.0
  • a8335a8 docs(release): move the vscode extension release steps to RELEASING.md
  • 9d151cc chore(release): bump version to 8.1.0
  • 6fc3384 docs(install): add uv tool install as an installation option
  • 83be163 Merge pull request #286 from rohaquinlop/issue-270-config-json-schema
  • 26f7bfc docs(config): document the configuration json schema
  • 9e637d7 feat(config): generate a json schema for the configuration
  • 941a844 chore(deps): add schemars and jsonschema for the config schema
  • Additional commits viewable in compare view

Updates ruff from 0.17.0 to 0.17.2

Release notes

Sourced from ruff's releases.

0.17.2

Release Notes

Released on 2026-10-22.

Preview features

  • [complexity] Add unnecessary-regular-expression-compile (#25533)

Bug fixes

  • Avoid syntax errors for type variables with starred constraints (UP040, UP046, UP047, RUF053) (#28362)
  • [pydocstyle] Treat backslash-escaped *args and **kwargs as documented (D417) (#29536)
  • [pylint] Avoid false positive on starred elements (PLE0643) (#29483)
  • [pylint] Mark fixes unsafe when deleting comments (PLR5501, PLW0120) (#29414)
  • [pyupgrade] Mark fix unsafe when deleting comments (UP035) (#29413)

Performance

  • Avoid intermediate names in lint name resolution (#29506)
  • Prefilter bidirectional Unicode checks by UTF-8 leading bytes (#29561)
  • Share postfix parsing and reduce expression copies (#29480)

Configuration

  • [pylint] Add a configurable allowlist for magic-value-comparison (PLR2004) (#18961)

Documentation

  • Clarify documentation and correct stale guidance (#29374)
  • [pyupgrade] Remove mentions of variance related to fix safety (UP040, UP047) (#29592)

Contributors

Install ruff 0.17.2

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/ruff/releases/download/0.17.2/ruff-installer.sh | sh
</tr></table>

... (truncated)

Changelog

Sourced from ruff's changelog.

0.17.2

Released on 2026-10-22.

Preview features

  • [complexity] Add unnecessary-regular-expression-compile (#25533)

Bug fixes

  • Avoid syntax errors for type variables with starred constraints (UP040, UP046, UP047, RUF053) (#28362)
  • [pydocstyle] Treat backslash-escaped *args and **kwargs as documented (D417) (#29536)
  • [pylint] Avoid false positive on starred elements (PLE0643) (#29483)
  • [pylint] Mark fixes unsafe when deleting comments (PLR5501, PLW0120) (#29414)
  • [pyupgrade] Mark fix unsafe when deleting comments (UP035) (#29413)

Performance

  • Avoid intermediate names in lint name resolution (#29506)
  • Prefilter bidirectional Unicode checks by UTF-8 leading bytes (#29561)
  • Share postfix parsing and reduce expression copies (#29480)

Configuration

  • [pylint] Add a configurable allowlist for magic-value-comparison (PLR2004) (#18961)

Documentation

  • Clarify documentation and correct stale guidance (#29374)
  • [pyupgrade] Remove mentions of variance related to fix safety (UP040, UP047) (#29592)

Contributors

0.17.1

Released on 2026-10-15.

Preview features

  • [pycodestyle] Don't treat None, True, or False as keywords (E271-E274) (#29322)

... (truncated)

Commits
  • 30516b4 Bump version to 0.17.2 (#29637)
  • 59a9e85 [ty] Generalize nested types in inferred return types (#29488)
  • 0d562aa [ty] Check inherited attribute conflicts (#28559)
  • 48dcdd0 [ty] Restrict range implications from gradual equivalence (#29577)
  • 734d75a [ty] Check for unsatisfiable bodies before existentially quantifying (#29504)
  • b0f9526 [ty] Preserve checks for recursive descriptor setter types (#29148)
  • 32869b4 Avoid creating deployments for automation jobs (#29626)
  • ec891ba Link the commit in pull request report footers (#29621)
  • 8958748 [ty] Publish ecosystem reports from GitHub Actions (#29609)
  • 01f5394 [ty] Publish typing conformance reports from GitHub Actions (#29608)
  • Additional commits viewable in compare view

Updates pytest-mock from 3.16.0 to 3.17.0

Release notes

Sourced from pytest-mock's releases.

v3.17.0

2026-10-17

  • #641: Failures of mock assertions such as assert_called_with are again reported only once, instead of two or three times with the original error from the mock module chained before them.
  • #642: Mock assertion failures no longer show misleading introspection when they are not about the arguments of the last call: assert_called, assert_called_once, assert_not_called, assert_any_call, their await counterparts, and assert_called_once_with/assert_awaited_once_with when the mock was not called (awaited) exactly once. The introspection also no longer reports arguments passed by position versus by keyword as different for autospecced mocks, and no longer shows empty Args:/Kwargs: sections when assertion rewriting is not available.
  • #643: assert_has_calls and assert_has_awaits failures no longer show pytest introspection, which compared the expected and actual calls position by position and so reported differences between unrelated calls. The mock's own message, listing the expected and actual calls, is still shown.

v3.16.1

2026-10-17

  • #617: Fixed assert_has_calls raising ValueError instead of AssertionError (or showing misleading introspection) when the expected calls are plain tuples rather than call(...) objects, such as (args, kwargs) entries of another mock's call_args_list, (args,), (kwargs,), (name, args) or (name, kwargs).
  • #621: Fixed mocker.stop() sometimes stopping the wrong mock, for example with mocks from mocker.create_autospec.
  • #621: mocker.stop() now undoes the most recent patch first when the same object is used in several patches.
  • #623: Fixed misleading introspection in assert_has_awaits failures, and assert_has_calls/assert_has_awaits raising IndexError instead of AssertionError when calls is passed by keyword.
  • #624: Clear spy_return_iter after a spied synchronous or asynchronous function raises, matching spy_return.
  • #627: Document async_stub await assertions and the distinction between call and await tracking.
  • #629: Fixed mocker.resetall() skipping the mocks patched with mocker.patch.multiple(), both the ones it creates and the ones passed explicitly.
  • #630: mocker.resetall() now also resets spy_return and spy_exception of spies, like it already did for spy_return_list and spy_return_iter, and no longer overwrites attributes with these names on mocks that are not spies.
  • #633: Fixed spies on classmethod, staticmethod, builtins and classes returning a MagicMock instead of calling the spied code after mocker.resetall(side_effect=True). Resetting a spy's side_effect now goes back to calling the spied code, also clearing any side_effect set on the spy.
Changelog

Sourced from pytest-mock's changelog.

3.17.0

2026-10-17

  • [#641](https://github.com/pytest-dev/pytest-mock/issues/641) <https://github.com/pytest-dev/pytest-mock/pull/641>_: Failures of mock assertions such as assert_called_with are again reported only once, instead of two or three times with the original error from the mock module chained before them.
  • [#642](https://github.com/pytest-dev/pytest-mock/issues/642) <https://github.com/pytest-dev/pytest-mock/pull/642>_: Mock assertion failures no longer show misleading introspection when they are not about the arguments of the last call: assert_called, assert_called_once, assert_not_called, assert_any_call, their await counterparts, and assert_called_once_with/assert_awaited_once_with when the mock was not called (awaited) exactly once. The introspection also no longer reports arguments passed by position versus by keyword as different for autospecced mocks, and no longer shows empty Args:/Kwargs: sections when assertion rewriting is not available.
  • [#643](https://github.com/pytest-dev/pytest-mock/issues/643) <https://github.com/pytest-dev/pytest-mock/pull/643>_: assert_has_calls and assert_has_awaits failures no longer show pytest introspection, which compared the expected and actual calls position by position and so reported differences between unrelated calls. The mock's own message, listing the expected and actual calls, is still shown.

3.16.1

2026-10-17

  • [#617](https://github.com/pytest-dev/pytest-mock/issues/617) <https://github.com/pytest-dev/pytest-mock/pull/617>_: Fixed assert_has_calls raising ValueError instead of AssertionError (or showing misleading introspection) when the expected calls are plain tuples rather than call(...) objects, such as (args, kwargs) entries of another mock's call_args_list, (args,), (kwargs,), (name, args) or (name, kwargs).
  • [#621](https://github.com/pytest-dev/pytest-mock/issues/621) <https://github.com/pytest-dev/pytest-mock/pull/621>_: Fixed mocker.stop() sometimes stopping the wrong mock, for example with mocks from mocker.create_autospec.
  • [#621](https://github.com/pytest-dev/pytest-mock/issues/621) <https://github.com/pytest-dev/pytest-mock/pull/621>_: mocker.stop() now undoes the most recent patch first when the same object is used in several patches.
  • [#623](https://github.com/pytest-dev/pytest-mock/issues/623) <https://github.com/pytest-dev/pytest-mock/pull/623>_: Fixed misleading introspection in assert_has_awaits failures, and assert_has_calls/assert_has_awaits raising IndexError instead of AssertionError when calls is passed by keyword.
  • [#624](https://github.com/pytest-dev/pytest-mock/issues/624) <https://github.com/pytest-dev/pytest-mock/pull/624>_: Clear spy_return_iter after a spied synchronous or asynchronous function raises, matching spy_return.
  • [#627](https://github.com/pytest-dev/pytest-mock/issues/627) <https://github.com/pytest-dev/pytest-mock/pull/627>_: Document async_stub await assertions and the distinction between call and await tracking.
  • [#629](https://github.com/pytest-dev/pytest-mock/issues/629) <https://github.com/pytest-dev/pytest-mock/pull/629>_: Fixed mocker.resetall() skipping the mocks patched with mocker.patch.multiple(), both the ones it creates and the ones passed explicitly.
  • [#630](https://github.com/pytest-dev/pytest-mock/issues/630) <https://github.com/pytest-dev/pytest-mock/pull/630>_: mocker.resetall() now also resets spy_return and spy_exception of spies, like it already did for spy_return_list and spy_return_iter, and no longer overwrites attributes with these names on mocks that are not spies.
  • [#633](https://github.com/pytest-dev/pytest-mock/issues/633) <https://github.com/pytest-dev/pytest-mock/pull/633>_: Fixed spies on classmethod, staticmethod, builtins and classes returning a MagicMock instead of calling the spied code after mocker.resetall(side_effect=True). Resetting a spy's side_effect now goes back to calling the spied code, also clearing any side_effect set on the spy.
Commits
  • 5c2f207 Release 3.17.0
  • 9625271 Bump the minor version for releases that change existing behavior
  • 34b87ae Drop introspection from assert_has_calls and assert_has_awaits (#643)
  • 866520f Only show introspection for failures about the call arguments (#642)
  • 5ab41c1 Do not chain the original mock error to wrapped assertion failures (#641)
  • 1916b14 Merge pull request #635 from nicoddemus/docs-contributing-resetall
  • 212fcd9 Document resetall, the changelog format and running tests with tox
  • 9374b2c Merge pull request #634 from pytest-dev/release-3.16.1
  • fab730d Release 3.16.1
  • d26d41b Merge pull request #627 from xiehuanyi/docs/async-stub-awaits-20261012-r2
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested a review from thorsten-klein as a code owner October 25, 2026 09:34
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Oct 25, 2026
@thorsten-klein thorsten-klein mentioned this pull request Oct 25, 2026
Merged
thorsten-klein added a commit that referenced this pull request Oct 25, 2026
@thorsten-klein @claude
ci: audit only the runtime dependencies with pip-audit (#181)
e107dd2 
Fixes the failing `Run Tests` workflow (e.g.
https://github.com/thorsten-klein/git-nested/actions/runs/40121601902),
which also blocks #179 and #180.

## Problem
`poe pip-audit` audited the whole dev environment. `filelock 3.32.3` has
CVEs (CVE-2026-112907, -112913, -112940) and the fix is in 4.2.1, which
needs Python >= 3.11. On 3.10 the newest version is 4.1.0, which has
three more CVEs. filelock is dev-only. It comes in through `pre-commit`
→ `virtualenv` and through `pip-audit` → `cachecontrol[filecache]`, and
it never ships with git-nested.

## Change
The `pip-audit` task now audits a `uv export --no-default-groups` of the
lock, so only the runtime dependencies that ship (currently PyYAML) are
checked. The export keeps environment markers, so each Python version in
CI audits its own resolved set.

## Testing
- `poe all` passes locally on 3.12.
- `poe pip-audit` passes on 3.10 and 3.12.
- Without this change, the same export-based audit run on 3.10 over the
full lock still reports the filelock CVEs.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@dependabot
build(deps-dev): bump the dev group across 1 directory with 3 updates
c345735 
Bumps the dev group with 3 updates in the / directory: [complexipy](https://github.com/rohaquinlop/complexipy), [ruff](https://github.com/astral-sh/ruff) and [pytest-mock](https://github.com/pytest-dev/pytest-mock).


Updates `complexipy` from 8.0.1 to 8.1.0
- [Release notes](https://github.com/rohaquinlop/complexipy/releases)
- [Changelog](https://github.com/rohaquinlop/complexipy/blob/main/CHANGELOG.md)
- [Commits](rohaquinlop/complexipy@8.0.1...8.1.0)

Updates `ruff` from 0.17.0 to 0.17.2
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ruff@0.17.0...0.17.2)

Updates `pytest-mock` from 3.16.0 to 3.17.0
- [Release notes](https://github.com/pytest-dev/pytest-mock/releases)
- [Changelog](https://github.com/pytest-dev/pytest-mock/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest-mock@v3.16.0...v3.17.0)

---
updated-dependencies:
- dependency-name: complexipy
  dependency-version: 8.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev
- dependency-name: pytest-mock
  dependency-version: 3.17.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev
- dependency-name: ruff
  dependency-version: 0.17.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title build(deps-dev): bump the dev group with 3 updates build(deps-dev): bump the dev group across 1 directory with 3 updates Oct 25, 2026
@dependabot
dependabot Bot force-pushed the dependabot/uv/dev-4561d91d2b branch from dca82d1 to c345735 Compare October 25, 2026 19:24
@thorsten-klein thorsten-klein mentioned this pull request Oct 25, 2026
Merged
@thorsten-klein

thorsten-klein commented Oct 25, 2026

Copy link
Copy Markdown
Owner

Superseded by #183, which is the same change opened from a maintainer account. Workflows started by Dependabot can't read the SONAR_TOKEN/CODECOV_TOKEN secrets, so CI can't pass here.

@dependabot @github

dependabot Bot commented on behalf of github Oct 25, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/uv/dev-4561d91d2b branch October 25, 2026 19:27
thorsten-klein added a commit that referenced this pull request Oct 25, 2026
@thorsten-klein @claude
build(deps-dev): bump the dev group across 1 directory with 3 updates (…
a1e0652 
…#183)

Recreates #180 under a maintainer account. Workflows started by
Dependabot can't read the Actions secrets (`SONAR_TOKEN`,
`CODECOV_TOKEN`), so the SonarCloud scan can't pass on a Dependabot PR.

Bumps the dev group with 3 updates in the / directory:
[complexipy](https://github.com/rohaquinlop/complexipy),
[ruff](https://github.com/astral-sh/ruff) and
[pytest-mock](https://github.com/pytest-dev/pytest-mock).

Updates `complexipy` from 8.0.1 to 8.1.0

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@thorsten-klein thorsten-klein Awaiting requested review from thorsten-klein thorsten-klein is a code owner

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@thorsten-klein