Bump dictdiffer from 0.9.0 to 0.10.0 - #726
Conversation
Bumps [dictdiffer](https://github.com/inveniosoftware/dictdiffer) from 0.9.0 to 0.10.0. - [Release notes](https://github.com/inveniosoftware/dictdiffer/releases) - [Changelog](https://github.com/inveniosoftware/dictdiffer/blob/master/CHANGES) - [Commits](inveniosoftware/dictdiffer@v0.9.0...v0.10.0) --- updated-dependencies: - dependency-name: dictdiffer dependency-version: 0.10.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
🔵 Review postedLast updated: 2026-08-01 01:15 UTC |
rtibblesbot
left a comment
There was a problem hiding this comment.
PR #726 — dictdiffer 0.9.0 → 0.10.0 (minor), production dependency (pyproject.toml:38, dictdiffer>=0.8.0). Lockfile-only diff, confined to the dictdiffer block. CI passing on all 12 unit-test jobs (ubuntu/macos/windows × 3.9–3.13) plus the docs build.
Breaking changes: none. Deprecations: none. Security fixes: none. Peer/transitive deps: none — v0.10.0 declares zero unconditional Requires-Dist (all behind docs/numpy/tests extras).
First release in 5 years, so I diffed the published 0.9.0 and 0.10.0 wheels directly. Beyond SPDX license-header rewrites and an import reflow, there are exactly two behavioral edits, both gated behind opt-in parameters:
diff(..., path_limit=...)no longer emits a spuriousCHANGEfor equal subtrees (#174)Merger.__init__gainsignore=None, threaded into its internaldiff()calls
Neither is reachable here: dictdiffer is imported only in ricecooker/utils/corrections.py:9, and both call sites (corrections.py:522, :546) are bare dictdiffer.diff(node_before, node_after) whose result is only printed. No path_limit, no Merger anywhere in the codebase.
Packaging notes, non-blocking: build backend moved setuptools → hatchling (sdist shrank 31.5 KB → 12.5 KB as tests/docs are no longer packaged), wheel tag narrowed to py3-none-any, and Requires-Python: >=3.7 is now declared. Ricecooker targets 3.9–3.13, so both are satisfied.
No code changes required.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
rtibbles
left a comment
There was a problem hiding this comment.
No concerns from changelog or tests.
Bumps dictdiffer from 0.9.0 to 0.10.0.
Changelog
Sourced from dictdiffer's changelog.
... (truncated)
Commits
1e6eb4erelease: v0.10.017f3b94chore(setup): migrate from setuptools to hatchlingfde6a4fchore(workflows): use the centralized GitHub actions1ae323echore(git-blame): ignore the SPDX license header commit1c6111cchore(licenses): update license headers to use SPDXbfb5dd4diff: fixpath_limitwith no change (#174)6719335merge: support ignore param to diff functionb32e4b0setup: populate python_requires >= 3.5 fieldDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)