Repository navigation
Preserve historical Torch pins and raise supported floor - #11
dependabot[bot] wants to merge 3 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 [torch](https://github.com/pytorch/pytorch) from 2.14.0+cpu to 2.14.1. - [Release notes](https://github.com/pytorch/pytorch/releases) - [Changelog](https://github.com/pytorch/pytorch/blob/main/RELEASE.md) - [Commits](https://github.com/pytorch/pytorch/commits/v2.14.1) --- updated-dependencies: - dependency-name: torch dependency-version: 2.11.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
900662c to
4dedc2d
Compare
OptimumAF
left a comment
There was a problem hiding this comment.
The refreshed diff rewrites recorded torch==2.14.0+cpu to 2.14.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.
OptimumAF
left a comment
There was a problem hiding this comment.
Reviewed exact repaired head b4df488. This resolves my prior requested change: only the supported torch floor becomes >=2.11,<3.0; torchvision and other requirements remain unchanged. The dated constraints blob063f067f0115ff22f1f5dc5039bb35b47ee76674 and environment blob37913942414f50e97766f4ece6cf5fa816612fad read back unchanged, so the original torch2.14.0+cpu evidence is preserved. All five exact-head CI jobs and the security check passed. No historical repin, package installation, producer publication or scientific/runtime admission is introduced. This approval does not bypass repository protection.
Retain the merged NumPy requirement and the supported Torch >=2.11,<3.0 floor. Preserve dated environment blobs and all scientific source. Ordinary branch refresh; current-head CI and repository protection remain required.
|
A newer version of torch 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 Torch minimum to 2.11 while retaining <3.0. Restore the dated Windows CPU snapshot's Torch 2.14.0+cpu pin rather than assigning a new version to retained 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.