Stop caching the depot registries when a local registry is used - #128
Merged
Merged
Conversation
A local registry is a git clone that `Pkg.Registry.update` advances by rebasing, and one that fails to rebase stays broken in the cache for every later run, so resolution quietly falls back to stale registry data and reports it as unsatisfiable compat bounds. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A local registry lives in the depot as a git clone rather than General's packed form, and
Pkg.Registry.updateadvances it by rebasing. A clone that fails to rebase stays broken in the cache for every later run, so the registry stops updating and a compat floor on a new version fails as unsatisfiable. Skip the registry cache where a local registry is used. Repos without one are unaffected.