chore(deps): consume released pararamio-aio 3.0.31 - #3
Merged
Conversation
Drop the dev-only [tool.uv.sources] override that pointed pararamio-aio at ../py-pararamio/packages/pararamio_aio for local development of the X-UserToken work. pararamio-aio 3.0.31 is now on PyPI and contains the user_token=AsyncPararamio kwarg, so the override is no longer needed. - pyproject.toml: remove [tool.uv.sources] block and its TODO preamble - packages/pararam-nexus-mcp/pyproject.toml: bump pararamio-aio>=3.0.13 to pararamio-aio>=3.0.31 - uv.lock: regenerated against PyPI; pararamio-core removed from the resolved set (aio 3.0.31 is self-contained) Verified end-to-end against api.pararam.io with a real X-UserToken after the upgrade: limited mode still boots cleanly, 11 tools register, get_chat returns chat metadata over the published aio. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
ivolnistov
added a commit
that referenced
this pull request
May 12, 2026
Drop the dev-only [tool.uv.sources] override that pointed pararamio-aio at ../py-pararamio/packages/pararamio_aio for local development of the X-UserToken work. pararamio-aio 3.0.31 is now on PyPI and contains the user_token=AsyncPararamio kwarg, so the override is no longer needed. - pyproject.toml: remove [tool.uv.sources] block and its TODO preamble - packages/pararam-nexus-mcp/pyproject.toml: bump pararamio-aio>=3.0.13 to pararamio-aio>=3.0.31 - uv.lock: regenerated against PyPI; pararamio-core removed from the resolved set (aio 3.0.31 is self-contained) Verified end-to-end against api.pararam.io with a real X-UserToken after the upgrade: limited mode still boots cleanly, 11 tools register, get_chat returns chat metadata over the published aio.
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
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
Drop the dev-only
[tool.uv.sources]override onpararamio-aiothat was used to consume the unreleased X-UserToken kwarg during PR #2.pararamio-aio 3.0.31is now on PyPI and contains that kwarg, so we can resolve normally.pyproject.toml: removed the[tool.uv.sources]block + its TODO preamble.packages/pararam-nexus-mcp/pyproject.toml: bumpedpararamio-aio>=3.0.13→pararamio-aio>=3.0.31.uv.lock: regenerated against PyPI;pararamio-corefalls out of the resolved set (aio 3.0.31 is self-contained).Why
PR #2 (the X-UserToken limited-mode work) was merged with the dev override still in place, which would have broken
uv syncfor fresh clones. This restores the repo to PyPI-only resolution.Test plan
uv lock --upgrade-package pararamio-aio+uv syncproduces a clean install ofpararamio-aio==3.0.31from PyPI (no local path).api.pararam.iowith a real X-UserToken: limited mode boots, 11 tools register,get_chat(360)returns real data over the published aio.