Skip to content

fix(deps): update dependency dreadnode to v2#166

Open
dreadnode-renovate-bot[bot] wants to merge 1 commit intomainfrom
renovate/dreadnode-2.x
Open

fix(deps): update dependency dreadnode to v2#166
dreadnode-renovate-bot[bot] wants to merge 1 commit intomainfrom
renovate/dreadnode-2.x

Conversation

@dreadnode-renovate-bot
Copy link
Copy Markdown
Contributor

@dreadnode-renovate-bot dreadnode-renovate-bot bot commented Apr 1, 2026 •
edited by github-actions bot
Loading

This PR contains the following updates:

| Package | Change | Age | Confidence |
|

Generated Summary:

  • Updated dreadnode dependency from version 1.17.1 to 2.0.7 in pyproject.toml.
  • Ensured compatibility with the new dreadnode release.

This summary was generated with ❤️ by rigging

| dreadnode | ==1.17.1 → ==2.0.7 | age | confidence |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 has been generated by Renovate Bot.

@dreadnode-renovate-bot
fix(deps): update dependency dreadnode to v2
4f2652c 
| datasource | package   | from   | to    |
| ---------- | --------- | ------ | ----- |
| pypi       | dreadnode | 1.17.1 | 2.0.7 |
@dreadnode-renovate-bot dreadnode-renovate-bot bot requested a review from a team as a code owner April 1, 2026 13:59
@dreadnode-renovate-bot
Copy link
Copy Markdown
Contributor Author

dreadnode-renovate-bot bot commented Apr 1, 2026

⚠️ 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: uv.lock
Command failed: uv lock --upgrade-package dreadnode
Using CPython 3.14.3 interpreter at: /opt/containerbase/tools/python/3.14.3/bin/python3
Resolving despite existing lockfile due to addition of global exclude newer 2026-03-29T13:59:47.863851369Z
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version >= '3.12'):
  ╰─▶ Because dreadnode==2.0.7 depends on xmltodict>=1.0.2 and rigging>=3.0.0
      depends on xmltodict>=0.13.0,<0.14.0, we can conclude that
      dreadnode==2.0.7 and rigging>=3.0.0 are incompatible.
      And because only the following versions of rigging are available:
          rigging<=3.0.0
          rigging==3.0.1
          rigging==3.0.2
          rigging==3.1.0
          rigging==3.1.1
          rigging==3.2.0
          rigging==3.2.1
          rigging==3.2.3
          rigging==3.3.0
          rigging==3.3.2
          rigging==3.3.4
          rigging==3.3.5
      we can conclude that dreadnode==2.0.7 and rigging>=3.0.0 are
      incompatible.
      And because your project depends on dreadnode==2.0.7 and rigging>=3.0.0,
      we can conclude that your project's requirements are unsatisfiable.

      hint: Pre-releases are available for `rigging` in the requested
      range (e.g., 3.0.3a0), but pre-releases weren't enabled (try:
      `--prerelease=allow`)

@dreadnode-renovate-bot dreadnode-renovate-bot bot added area/python Changes to Python package configuration and dependencies type/digest Dependency digest updates labels Apr 1, 2026
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

area/python Changes to Python package configuration and dependencies type/digest Dependency digest updates

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants