chore(deps): bump iohub to >=0.3.10#482
Open
edyoshikun wants to merge 1 commit into
Open
Conversation
Bump the iohub lower bound from 0.3.6 to 0.3.10 across all packages and applications, and regenerate uv.lock. The lockfile diff is large because the committed lock had drifted from the pyproject constraints; uv re-resolved the full graph to a consistent state. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Member
Author
|
I wasn't sure if we wanted to update all our packages or just the ones that need it. We can edit it as needed. |
srivarra
approved these changes
Jul 22, 2026
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
Bumps the
iohublower bound from>=0.3.6to>=0.3.10(latest release) across all packages and applications:applications/airtableapplications/dynacellapplications/dynaclrpackages/viscy-datapackages/viscy-utilsLockfile
uv.lockwas regenerated. The diff is large (~2400 lines) because the committed lock had drifted from the pyproject constraints —uv lockre-resolved the full graph to a consistent state. iohub now resolves to0.3.10.Test plan
🤖 Generated with Claude Code