Repository navigation
feat(crons): Add monitor environment deletion tool - #1443
Merged
evanpurkhiser merged 1 commit intoOct 7, 2026
Merged
Conversation
evanpurkhiser
enabled auto-merge (squash)
October 7, 2026 20:47
evanpurkhiser
deleted the
git/feat-crons-add-monitor-environment-deletion-tool
branch
October 7, 2026 20:49
This branch was successfully deployed
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.
Add a catalog-only
delete_monitor_environmenttool so cron cleanup can remove an exact environment from a monitor. The tool requires the organization, project, monitor slug or GUID, and environment name, enforces project constraints, and schedules deletion while preserving the monitor and its other environments. Repeated deletion of an absent environment succeeds.Includes API client support, generated tool definitions, and tests for catalog discovery and dispatch, constraints, exact environment names, and API failures.
Validation: build, lint, workspace typechecks, and all 1,763 MCP core tests pass. The full workspace test run encountered 22 failures across four unrelated CLI test files.