Skip to content

chore: bump devhelm SDK floor to >=0.7.2#24

Merged
caballeto merged 1 commit into
mainfrom
chore/bump-devhelm-0.7.2
May 6, 2026
Merged

chore: bump devhelm SDK floor to >=0.7.2#24
caballeto merged 1 commit into
mainfrom
chore/bump-devhelm-0.7.2

Conversation

@caballeto
Copy link
Copy Markdown
Member

Summary

  • Bump devhelm dependency floor from >=0.6.0 to >=0.7.2
  • Refresh uv.lock (devhelm 0.7.0 → 0.7.2)

Why

Older devhelm versions (≤0.7.1) don't know about the managedBy field that the API now returns on resource DTOs (status pages, monitors, etc.), causing Pydantic extra_forbidden errors in real MCP tool calls.

devhelm 0.7.2 (just published to PyPI) carries:

  • managedBy field on all resource DTOs
  • New monitor validation contract (frequencySeconds bounds, dynamic region whitelist)

Aligns the MCP server with the cli / sdk-js v0.7.2 release.

Test plan

  • uv run python -m pytest tests/ → 135 passed locally
  • CI green
  • Surface integration tests on mono pass against the bumped lock

Made with Cursor

The 0.6.x and 0.7.0/0.7.1 lines of devhelm don't know about the
managedBy field that the API now returns on resource DTOs (status pages,
monitors, etc.). Pydantic raises extra_forbidden on every read, breaking
real-world MCP tool calls.

Floor bumped to 0.7.2, which also brings the new monitor validation
contract (frequencySeconds bounds, dynamic region whitelist) and keeps
us aligned with the cli/sdk-js v0.7.2 release.

Co-authored-by: Cursor <cursoragent@cursor.com>
@caballeto caballeto merged commit aca33be into main May 6, 2026
4 checks passed
@caballeto caballeto deleted the chore/bump-devhelm-0.7.2 branch May 6, 2026 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant