Refresh the lock: agentscore-py 2.6.6, lefthook 2.1.11 - #120
Merged
Conversation
prerelease = "disallow" is already in place here, and the new lock was swept for a/b/rc versions after resolving: zero, which is the check that entry exists for. The same guard is going into python-sdk and core's three Python projects, since it was only ever here. No version bump: a lockfile refresh reaches no consumer, since the published wheel does not ship the lock. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
Lock refresh:
agentscore-py2.6.5 to 2.6.6 andlefthook2.1.10 to 2.1.11.prerelease = "disallow"is already in place here, and the new lock was swept fora/b/rcversions after resolving: zero, which is the check that entry exists for. The same guard is going into python-sdk and core's three Python projects in their own PRs, since it was only ever here.Type of change
Public API
None.
No version bump, deliberately. The runbook releases only where a consumer must act, and a lockfile refresh reaches nobody: the published wheel does not ship the lock, and
agentscore-pyresolves through this package's declared range either way.Test plan
Full gate set locally:
ruff check,ruff format --check(216 files),ty check,vulture(run the repo's own way, which takes no whitelist file here), andpytest(1863 passed, 4 skipped, 95.37% against a 95% floor). Exit codes read directly rather than off the tail of a pipe, after a first attempt readtail's status instead of vulture's.Also confirmed the lock still embeds the project's own version (2.7.1), since a version bump without a re-lock leaves the two disagreeing and nothing errors.
Checklist