Skip to content

docs(changelog): runner enrollment via dashboard, regrouped nav, retry idempotency#79

Merged
indykish merged 3 commits into
mainfrom
chore/m84-changelog
Jun 4, 2026
Merged

docs(changelog): runner enrollment via dashboard, regrouped nav, retry idempotency#79
indykish merged 3 commits into
mainfrom
chore/m84-changelog

Conversation

@indykish

@indykish indykish commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Changelog entry for the M84 work — runner enrollment from the dashboard, the regrouped dashboard navigation, and the Hypertext Transfer Protocol (HTTP) retry-idempotency change. Pairs with usezombie/usezombie#365.

What changed

  • New Jun 04, 2026 <Update> block in changelog.mdx.
  • Covers:
    • Dashboard runner enrollment via a one-time runner token (platform-admin login never touches a shell).
    • Honest derived liveness on the runner list (registered until first check-in, not a false online).
    • Left-nav regroup into Operations / Configuration / Organization, with model settings moved to their own Model entry at /settings/models.
    • Removal of zombie-runner register and its --token / --host-id flags.
    • GET /v1/fleet/runners (platform-admin only, paginated, never returns the token hash).
    • 5xx retries now gated to idempotent methods only; POST/PATCH surface failures immediately.

Notes

  • Documentation-only; no code change in this repo.

Greptile Summary

This PR adds a single <Update> block to changelog.mdx documenting three M84 changes: dashboard-based runner enrollment via a one-time token, a regrouped left navigation, and a new rule limiting 5xx retries to idempotent HTTP methods.

  • Runner enrollment — replaces zombie-runner register with a dashboard flow; the Upgrading section now lists all removed flags (--token, --host-id, ZOMBIE_TOKEN) and the new ZOMBIE_RUNNER_TOKEN variable; the CLI section cross-references Upgrading without duplication.
  • Navigation regroup — documents the Operations / Configuration / Organization split and the new /settings/models path.
  • Retry idempotency — documents that POST/PATCH failures now surface immediately rather than being retried, with network errors and 429/503/504 responses unchanged.

Confidence Score: 5/5

Documentation-only change; no runtime code is modified.

The PR adds a single changelog block. The content is accurate, internally consistent, matches the existing file conventions, and the previously flagged issues (missing --host-id in Upgrading, CLI/Upgrading duplication) are both addressed in the current version.

No files require special attention.

Important Files Changed

Filename Overview
changelog.mdx New Jun 04, 2026 Update block documenting runner dashboard enrollment, left-nav regroup, and HTTP retry idempotency changes; no code changes, consistent with file's existing structure and conventions.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[HTTP Request] --> B{Idempotent method?\nGET / PUT / DELETE / HEAD}
    B -- Yes --> C{Response}
    B -- No\nPOST / PATCH --> D[Surface error immediately]
    C -- 5xx server error --> E[Retry]
    C -- Network error --> E
    C -- 429 / 503 / 504 --> E
    C -- 2xx --> F[Success]
    E --> A
Loading

Reviews (3): Last reviewed commit: "docs(changelog): drop dead #upgrading an..." | Re-trigger Greptile

…y idempotency

Jun 04, 2026 entry: enroll runners from the dashboard (Add runner mints a
one-time token; fleet list with derived liveness), the regrouped left nav
(Operations / Configuration / Organization) with the model settings at
/settings/models, the removal of `zombie-runner register`, and the server-5xx
idempotency gate on the dashboard + zombiectl HTTP clients.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Comment thread changelog.mdx Outdated
Comment thread changelog.mdx Outdated
…-id to Upgrading

Greptile review on PR #79:
- P1: --host-id removal was missing from the Upgrading migration guide;
  the Upgrading bullet now lists --token, --host-id, and ZOMBIE_TOKEN.
- P2: the CLI section duplicated the Upgrading removal notice with
  divergent flag lists; the CLI bullet is now a terse cross-reference
  pointing to Upgrading for the full enrollment flow.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jun 4, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
megam 🟢 Ready View Preview Jun 4, 2026, 4:33 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

…rence

Headings inside <Update> JSX blocks don't generate resolvable anchors,
so [Upgrading](#upgrading) failed the mintlify-link-check lint with a
404. Replaced the link with a plain **Upgrading** above prose reference.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@indykish indykish merged commit 962a39e into main Jun 4, 2026
4 checks passed
@indykish indykish deleted the chore/m84-changelog branch June 5, 2026 09:25
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