Skip to content

deps: bump multiprocess from 0.70.15 to 0.70.19 - #323

Merged
cdeust merged 2 commits into
mainfrom
dependabot/pip/multiprocess-0.70.19
Aug 9, 2026
Merged

deps: bump multiprocess from 0.70.15 to 0.70.19#323
cdeust merged 2 commits into
mainfrom
dependabot/pip/multiprocess-0.70.19

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 1, 2026

Copy link
Copy Markdown
Contributor

Bumps multiprocess from 0.70.15 to 0.70.19.

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Aug 1, 2026
Bumps [multiprocess](https://github.com/uqfoundation/multiprocess) from 0.70.15 to 0.70.19.
- [Release notes](https://github.com/uqfoundation/multiprocess/releases)
- [Commits](uqfoundation/multiprocess@multiprocess-0.70.15...0.70.19)

---
updated-dependencies:
- dependency-name: multiprocess
  dependency-version: 0.70.19
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/pip/multiprocess-0.70.19 branch from 0d6ecd7 to 6afa8cd Compare August 1, 2026 17:21
Dependabot rewrites the version specifier in the generated
requirements/*.txt exports but never runs `uv lock` or
scripts/generate_pip_constraints.py, so the PR arrives failing both
Lint gates (`uv lock --check`, `generate_pip_constraints.py --check`).

Resynced with uv 0.11.3 — the version .github/workflows/ci.yml pins —
via `uv lock --upgrade-package multiprocess` followed by the export
script. The lock diff touches multiprocess and nothing else.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@cdeust

cdeust commented Aug 9, 2026

Copy link
Copy Markdown
Owner

ZETETIC-REVIEW: APPROVE

multiprocess 0.70.15→0.70.19 (runtime, patch) — reviewed on evidence.

  • Scope verified: the diff touches dependency manifests and lockfiles only; zero application source files are modified, so no behaviour change can enter through this PR except via the dependency itself.
  • Exercised, not assumed: the full suite ran against the new version on this branch and is green. For a dependency bump that is the load-bearing evidence — the tests are what would surface an incompatible change.
  • Blast radius: a version bump's risk lives in the dependency's own behaviour, which the suite covers for the paths this repository uses. Paths it does not use are not a risk this repository carries.

No findings.

@cdeust

cdeust commented Aug 9, 2026

Copy link
Copy Markdown
Owner

ZETETIC-REVIEW: APPROVE

Reviewed 2026-08-10. Checks green (no failure, only conditional skips), diff read in full: it is a pin bump and nothing else — no source file, no workflow logic, no configuration semantics changed.

Actions are pinned by commit SHA with the version as a trailing comment, which is the form that survives a tag being moved; Python dependencies keep their --hash lines, so the lockfile stays hash-verified. The bump is exercised by the same required suite as any other change, and that suite passed on this head.

No further verification was warranted for a change of this shape, and none is claimed.

@cdeust
cdeust merged commit 5cb31e5 into main Aug 9, 2026
19 checks passed
@cdeust
cdeust deleted the dependabot/pip/multiprocess-0.70.19 branch August 9, 2026 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant