chore(deps): regen uv.lock to match pinned versions in pyproject#28094
Merged
Conversation
uv.lock drifted from pyproject.toml after the CVE bumps (#26830) and the 0.14.0 release. The installer's hash-verified tier was failing `uv pip sync --locked` and falling back to unlocked PyPI resolve, producing two warnings on every fresh install. Regen aligns the lockfile: - aiohttp 3.13.4 -> 3.13.3 (matches messaging/slack/homeassistant/sms pin) - anthropic 0.87.0 -> 0.86.0 (matches anthropic extra pin) - hermes-agent 0.13.0 -> 0.14.0 (matches project version) No behavioral changes. `uv lock --check` now passes.
Contributor
🔎 Lint report:
|
19 tasks
Lillard01
pushed a commit
to Lillard01/hermes-agent
that referenced
this pull request
May 21, 2026
…sResearch#28094) uv.lock drifted from pyproject.toml after the CVE bumps (NousResearch#26830) and the 0.14.0 release. The installer's hash-verified tier was failing `uv pip sync --locked` and falling back to unlocked PyPI resolve, producing two warnings on every fresh install. Regen aligns the lockfile: - aiohttp 3.13.4 -> 3.13.3 (matches messaging/slack/homeassistant/sms pin) - anthropic 0.87.0 -> 0.86.0 (matches anthropic extra pin) - hermes-agent 0.13.0 -> 0.14.0 (matches project version) No behavioral changes. `uv lock --check` now passes.
Mucky010
pushed a commit
to Mucky010/hermes-agent
that referenced
this pull request
May 24, 2026
…sResearch#28094) uv.lock drifted from pyproject.toml after the CVE bumps (NousResearch#26830) and the 0.14.0 release. The installer's hash-verified tier was failing `uv pip sync --locked` and falling back to unlocked PyPI resolve, producing two warnings on every fresh install. Regen aligns the lockfile: - aiohttp 3.13.4 -> 3.13.3 (matches messaging/slack/homeassistant/sms pin) - anthropic 0.87.0 -> 0.86.0 (matches anthropic extra pin) - hermes-agent 0.13.0 -> 0.14.0 (matches project version) No behavioral changes. `uv lock --check` now passes.
gweeteve
pushed a commit
to gweeteve/hermes-agent
that referenced
this pull request
Jun 2, 2026
…sResearch#28094) uv.lock drifted from pyproject.toml after the CVE bumps (NousResearch#26830) and the 0.14.0 release. The installer's hash-verified tier was failing `uv pip sync --locked` and falling back to unlocked PyPI resolve, producing two warnings on every fresh install. Regen aligns the lockfile: - aiohttp 3.13.4 -> 3.13.3 (matches messaging/slack/homeassistant/sms pin) - anthropic 0.87.0 -> 0.86.0 (matches anthropic extra pin) - hermes-agent 0.13.0 -> 0.14.0 (matches project version) No behavioral changes. `uv lock --check` now passes.
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.
Summary
Stops the two warnings users see on fresh install ("lockfile needs to be updated, but --locked was provided" + "installed via fallback tier"). uv.lock drifted from pyproject.toml after the CVE bumps in #26830 and the 0.14.0 release, so the installer's hash-verified tier was rejecting the lockfile and falling back to unlocked PyPI resolve on every fresh install.
Changes
uv.lock: regen viauv lock. Three version corrections to match pyproject pins:No behavioral changes — pure dependency lockfile alignment.
Validation
uv lock --checkbefore:The lockfile at uv.lock needs to be updateduv lock --checkafter:Resolved 213 packages in 1ms(clean)Reported by community user MoBai.