Fix v0.3.0 package build configuration - #526
Merged
Merged
Conversation
The hatch build configuration added in v0.3.0 was breaking package discovery, resulting in wheels that contained only metadata without the actual elroy Python code. Root cause: Using packages = ["elroy"] in [tool.hatch.build.targets.wheel] put hatch into explicit mode but didn't properly configure the package path, preventing auto-discovery of the elroy package directory. Fix: Remove the explicit packages directive to restore hatch's default auto-discovery behavior, and use force-include instead to add the claude-skills directory. This restores the working behavior from v0.2.0 while maintaining the claude-skills inclusion needed for v0.3.0's Claude Code integration. Co-Authored-By: Claude Sonnet 4.5 <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
1 participant
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.
Fixes the broken package build that was causing ModuleNotFoundError in the release CI.
Root Cause
The hatch build configuration added in v0.3.0 used
packages = ["elroy"]which put hatch into explicit mode but didn't properly configure the package path. This prevented auto-discovery of the elroy package directory, resulting in wheels that contained only metadata without the actual Python code.Solution
packagesdirective to restore hatch's default auto-discoveryforce-includeto add the claude-skills directoryThis restores the working behavior from v0.2.0 while maintaining claude-skills inclusion.
Testing