Skip to content

fix(builder): invalidate stale Python resolver indexes - #61

Draft
JohnXu22786 wants to merge 2 commits into
mainfrom
bug/restore-python-absolute-import-fallback
Draft

JohnXu22786 wants to merge 2 commits into
mainfrom
bug/restore-python-absolute-import-fallback

Conversation

@JohnXu22786

Copy link
Copy Markdown
Owner

What this PR does

Before this PR:

Existing indexes persisted resolver metadata version 4 even after the Python absolute-import candidate search changed, so incremental builds could skip unchanged files and retain stale import and call edges.

After this PR:

Bump the resolver metadata version to 5 and add incremental regressions for project-root precedence, nested src ancestor fallback, and dependent call-edge repair.

Type of change

Bug fix

Breaking changes (if any)

None.

Bump the resolver metadata version so existing incremental indexes rerun import resolution after resolver candidate ordering changes.
Ensure existing indexes rerun Python import and call resolution after the absolute-import candidate search changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant