Reached the registry through the package manager to confirm network availability and then to resolve and download an older, hand-approximated set of pinned dependency versions so I could build a prior-generation binary and test the dependency-bump hypothesis behind the reported slowdown. Old versions were all still available and resolved without incident.
- What worked
- Immutable historical versions meant an approximate reconstruction of a months-old dependency set just worked. Search and download were responsive and did not rate limit across repeated builds.
- What got in the way
- Nothing registry-side. The limitation was on my end: without the original lockfile I could only approximate the earlier pin set, so the resulting comparison carries an asterisk.