Repository navigation
Preserve historical torchvision pins and raise supported floor - #8
dependabot[bot] wants to merge 2 commits into
Conversation
|
@dependabot rebase Reviewed the single dependency/action change. Please refresh against current master, preserving current requirements and immutable dated experiment constraints. Existing green checks predate the five-job platform/CPU CI; refreshed checks are needed before merge. |
Bumps [torchvision](https://github.com/pytorch/vision) from 0.29.0+cpu to 0.29.1. - [Release notes](https://github.com/pytorch/vision/releases) - [Commits](https://github.com/pytorch/vision/commits/v0.29.1) --- updated-dependencies: - dependency-name: torchvision dependency-version: 0.26.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
53f6372 to
c392d4e
Compare
OptimumAF
left a comment
There was a problem hiding this comment.
The refreshed diff rewrites recorded torchvision==0.29.0+cpu to 0.29.1 in constraints/windows-cpu-py314-2026-10-06.txt.
This dated snapshot records an existing experiment environment. docs/dependency-reproducibility.md explicitly requires keeping such constraints immutable, retaining original versions and provenance, and adding a separately dated snapshot for a new environment. Restore the original constraints file byte-for-byte; do not relabel historical environments. Keep this PR scoped to justified development requirements, then run current-base CI. Green checks would not cure an overwritten evidence record.
|
A newer version of torchvision exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
Raise the supported torchvision minimum to 0.26 while retaining the <1.0 ceiling. Restore the dated Windows CPU constraint snapshot rather than overwrite its torchvision 0.29.0+cpu evidence.
Source readback confirms a one-line requirements-resnet.txt diff against current master and exact original bytes for both dated constraint/environment files. No installed campaign environment or scientific acceptance is changed. Current-head CI is required before merge.