docs(changelog): every runner lease says whose workspace it belongs to - #168
Merged
Conversation
Covers the runner lease workspace filter, the 30-day retention window for
settled leases and their activity records, the startup-posture copy split,
the account-teardown schedule unregister, and the write-time lifetime
counters behind the runner page.
Load-bearing facts kept verbatim: the workspace_id filter on
GET /v1/fleets/runners/{id}/leases, its UZ-REQ-001 refusal, the
agentsfleet_account_teardown_unregister_failures_total counter, and the
30-day window.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…entry
The Jul 31 runner-lease entry predates the review fixes it ships with.
Revised: the 30-day window is measured from settlement, not acquisition;
only the two per-lease activity records are pruned and the Activity feed
is kept at any age; four migrations apply, not three; starting_after
composes with the workspace_id filter and answers 400 UZ-REQ-001 across
filter contexts; one failed schedule unregister no longer strands the
rest; missing provider credentials count as failures; concurrent
deletions no longer starve the unregister pass of pool connections.
Load-bearing facts kept verbatim: GET /v1/fleets/runners/{id}/leases,
UZ-REQ-001, agentsfleet_account_teardown_unregister_failures_total, the
30-day window. History untouched: the M151 entry and older entries carry
through the rebase verbatim.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ay out The second review round added two user-visible behaviours the entry did not carry: a lease whose runner died on a fleet never used again is marked expired once it passes the retention window and then keeps its own window like any settled lease, and a bookmarked lease page the server refuses now links to the newest leases instead of prescribing a refresh that replays the same address. 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.
Changelog entry for M149_001 — the runner lease workspace correlation and bounded read paths. Ships with agentsfleet/agentsfleet#584.
What the entry covers
GET /v1/fleets/runners/{id}/leases.?workspace=<id>filter.workspace_idfilter, its400on a malformed value, and the empty-page answer for a well-formed identifier that owns nothing.Notes
Rebased onto
mainafter M148's entry (#167) landed; both entries carry the same date, and this one sits above it because it ships second. No other page needed revision — the workstream adds no error code and no scope, and no published page documents the operator runner surface. Behavior that is documented (the lease endpoint's filter and the retention window) is stated in the entry's Upgrading and API reference sections.🤖 Generated with Claude Code
Greptile Summary
Adds a changelog entry for runner lease workspace correlation and bounded history reads.
Confidence Score: 5/5
The documentation-only PR appears safe to merge.
The new entry follows existing changelog structure and tag conventions, and its API, retention, migration, and UI descriptions do not conflict with an established published contract.
Important Files Changed
Reviews (1): Last reviewed commit: "docs(changelog): the abandoned-lease rea..." | Re-trigger Greptile
Context used: