Repository navigation
0.3.0 - #154
Merged
Merged
0.3.0#154
Conversation
The first release since 0.2.3 (2026-03-19): the cleanup (#103), the browser app, finetuning in both modes, serving on chunkmirage, the worldarray reader, the consolidation (#150) and the paint logic written once (#152), as the changelog's Unreleased section listed them; it is dated here. The version moves in the three places that carry it (the package, pixi.toml, Fileglancer's runnables.yaml). The commands from before 0.3.0 keep working as aliases this release and go in the next, with the shims, once salamander, skoots-mito and cellmap-analyze have moved off them. The pyproject comment on painting names the neuroglancer fork commit pixi pins, not the moving branch. Claude-Session: https://claude.ai/code/session_01EzWMS4pG3tm1ZtvKULfSfW
…e doctor's fork install to pixi's commit The PyPI release depends on upstream neuroglancer, whose client has none of the paint fork's tools; the fork is installed by pixi. A pip install now hears why at start (cli.doctor.painting_unavailable, the doctor's check), with the install line, and that line names the commit pixi pins instead of the fork's branch; tests/web/test_pins.py keeps the two the same. Claude-Session: https://claude.ai/code/session_01EzWMS4pG3tm1ZtvKULfSfW
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.
Bumps the version to 0.3.0 in the three places that carry it (
cellmap_flow/__init__.py,pixi.toml, Fileglancer'srunnables.yaml) and dates the changelog's Unreleased section, which lists everything since 0.2.3 (2026-03-19): the cleanup (#103), the browser app, finetuning in both modes, serving on chunkmirage, the worldarray reader, the consolidation (#150) and the paint logic written once (#152).Publishing: merging this and pushing the tag
0.3.0on the merge commit runs.github/workflows/publish.yaml, which builds and uploads to PyPI (the token secret, as the workflow is written). Checked locally on this commit:python -m buildandtwine checkpass; the wheel installs onlycellmap_flow; its 48 requirements carry no direct URL (the earlierchunkmirage @ git+…would have made PyPI refuse the upload; it ischunkmirage>=0.1.0a2,<0.2since #152),worldarray>=0.1,<1and upstreamneuroglancer.What a pip install gets vs pixi: viewing, inference and training work from PyPI; painting in server mode also needs the neuroglancer voxel-annotation fork (not on PyPI;
pip install git+https://github.com/briossant/neuroglancer@fae54db8…, the commitpixi.tomlpins — the pyproject comment now names it) and the MinIO binaries (conda-forge). pixi and the Fileglancer deployment get both from the lockfile as before.Kept this release, deliberately: the pre-0.3.0 console scripts (
cellmap_flow_yaml,_view,_blockwise,_blockwise_multiple,_app,_server) and the compatibility shims. salamander calls the scripts in 34 files and imports five private names; skoots-mito callscellmap_flow_blockwisetwice. They go in the release after this one, once those repositories have moved tocellmap_flow <subcommand>.The neuroglancer fork, decided
The wheel depends on upstream
neuroglancerfrom PyPI; the paint fork (google/neuroglancer#858, not on PyPI) stays pixi's. Sopip install cellmap-flowserves models and runs the inference dashboard, and painting needs pixi or the fork's git install. Two fixes in the last commit make that visible instead of silent: the dashboard logs one warning at start when the installed neuroglancer cannot paint, with the install line, andcellmap_flow doctor's install line names the commit pixi pins (a test keeps the two together). Publishing the fork on PyPI under its own name was weighed and left for when pip users who paint show up.https://claude.ai/code/session_01EzWMS4pG3tm1ZtvKULfSfW