chore: bump ipsdk dependency floor to >=0.9.0 - #411
Merged
Conversation
Bump the ipsdk dependency floor from >=0.7.0 to >=0.9.0 to reflect the tested-and-confirmed-safe baseline. ipsdk 0.9.0 adds a new logging API (get_logger/reset_logger/register_logger_prefix) and Response timing fields (started_at/finished_at/elapsed_ms), with a breaking Response.__init__ signature change to keyword-only started_at/finished_at. itential-mcp has no call sites constructing ipsdk.Response directly and no usage of ipsdk.fatal(), so neither the breaking change nor the new API surface has any impact on this codebase. Confirmed via full unit suite (2858 passed) and live platform integration testing (get_health, get_devices, get_jobs). No source code changes required beyond the dependency declaration and lockfile update.
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
Bumps the
ipsdkdependency floor from>=0.7.0to>=0.9.0.Changes
pyproject.toml:ipsdk>=0.7.0→ipsdk>=0.9.0uv.lock: resolvesipsdk0.8.0 → 0.9.0 (from PyPI)Why
ipsdk0.9.0 was just released (itential/ipsdk#131, tagv0.9.0) as a MINOR bump containing:get_logger,reset_logger,register_logger_prefix)Responsetiming fields (started_at,finished_at,elapsed_ms) — this also makesResponse.__init__requirestarted_at/finished_atas keyword-only arguments, a breaking change for directResponseconstructionConfirmed itential-mcp has no call sites constructing
ipsdk.Responsedirectly and no usage ofipsdk.fatal()(whose behavior also changed in this range), so neither breaking change affects this codebase.Testing
feature-builder:make format/make check/make test— all passcode-quality-validator: lint, security (bandit), license headers, full test suite (2858 passed), coverage at baseline (98%) — PASSintegration-tester: live run against a real Itential Platform (not mocks) on this exact branch — connection/auth, 77 tools registered, liveget_health/get_devices/get_jobscalls, unit suite, plus a 404 error-path check and a debug-log plugin-load scan — GO, no regressionspr-evaluator: re-ranmake ciindependently (clean), verified branch/commit hygiene and push-target correctness — READY TO PUSHNo source code changes — dependency floor and lockfile only.
🤖 Generated with Claude Code