Migrate to monorepo with higlass-schema
subpackage
#190
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.
This PR migrates
higlass-schema
from its own repository into thehiglass-python
monorepo using uv workspaces. Previously, higlass-python depended on higlass-schema as an external PyPI package. Now both packages live together in a monorepo, allowing us to develop and test them in tandem.❯ tree --level=3 . ├── docs/ ├── examples/ ├── packages │ └── higlass-schema │ ├── src │ ├── tests │ ├── LICENSE │ ├── pyproject.toml │ ├── README.md │ └── uv.lock ├── src/ ├── test/ ├── deno.json ├── LICENSE ├── PR.md ├── pyproject.toml ├── README.md └── uv.lock
The main benefit is that we can make changes to both packages atomically - no more coordinating releases just to test integration changes. Both packages share the same linting, formatting, testing setup.
TODO:
higlass-python-v1.0.0
,higlass-schema-v1.0.0
) with automated PyPI publishing.Once this is merged, we can archive the original higlass-schema repository.