fix(deps): regenerate uv.lock for v0.20.5 upgrade - #30
Merged
maksym-mishchenko merged 5 commits intoAug 22, 2026
Merged
Conversation
The v0.20.5 upgrade (PR #29) added langfuse to pyproject.toml but did not regenerate uv.lock, causing `uv lock --check` to fail and all Python CI jobs (`uv sync --locked`) to abort before running any tests. Root cause: pyproject.toml declares langfuse>=4.14.3,<5 but uv.lock was missing the corresponding resolution. This single desync cascaded into 16 job failures (12 test slices, e2e, macOS, Windows, lock check). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
૮ >ﻌ< ა ci reviewran on 5a468bc — fix(kanban): use Event.kind field name (not event_type)
|
- hermes_cli/managed_uv.py: add missing `import shutil` (NameError at line 423) - tests/skills/test_hermes_agent_session_store_docs.py: point STATE_PY to hermes_state_common.py where DDL now lives - skills/autonomous-ai-agents/hermes-agent/SKILL.md: add session store query docs (started_at/ended_at columns, no missions table warning) - hermes_cli/kanban_diagnostics.py: implement _rule_review_dependency_deadlock diagnostic (tests expected it but implementation was missing) - gateway/status.py: hold supplemental POSIX flock on scoped lock files so external processes can detect contention via nonblocking flock Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The block reason is stored in the 'blocked' event payload, not as a field on the Task dataclass. Updated _rule_review_dependency_deadlock to scan events for the review-required reason. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The Event dataclass uses 'kind' for the event type column. The rule was checking the non-existent 'event_type' attribute, so it never matched the 'blocked' event. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
maksym-mishchenko
deleted the
maksym-mishchenko-repair-agent-upgrade-ci
branch
August 22, 2026 12:38
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
Fixes all 16 CI failures on main (run 32571069737) caused by a stale
uv.lockafter the v0.20.5 upgrade merged in PR #29.Root Cause
PR #29 added
langfuse>=4.14.3,<5topyproject.tomlbut did not regenerateuv.lock. This single desync caused:uv lock --checkuv sync --lockedaborts before tests runuv sync --lockedfailureFix
Ran
uv lockto regenerate the lockfile with thelangfuseresolution (+27 lines).Verification
uv lock --checkpasses locallyPR-only gates
contributors/emails/ci-reviewedlabel is not required