Fix migration not registering species after pip upgrade#6
Merged
Conversation
After `pip install -U`, pip replaces the package HCRconfig.yaml with a
fresh copy (species: {}), so the migration found and copied index files
but had no species entries to migrate. Now, when index directories are
migrated, they are auto-registered as species entries using the directory
name as both the species key and index prefix.
Bump version: 0.3.1 -> 0.3.2
https://claude.ai/code/session_01L9BrYriTeA72fsqqTvgdxy
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
2 participants
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
pip install -Ureplaced the packageHCRconfig.yamlwith a freshspecies: {}, causing migration to copy index files but not register species entriesTest plan
pip install -Uand verifylistReferencesshows auto-registered specieshttps://claude.ai/code/session_01L9BrYriTeA72fsqqTvgdxy