Skip to content

Document fleet changes in Unreleased changelog - #582

Draft
Finesssee wants to merge 1 commit into
mainfrom
changelog/unreleased-fleet
Draft

Finesssee wants to merge 1 commit into
mainfrom
changelog/unreleased-fleet

Conversation

@Finesssee

Copy link
Copy Markdown
Collaborator

Summary

Document the merged 38-PR porting fleet (upstream 0.60.4 → 0.62.0 lane) in a new top-level ## Unreleased changelog section, above the [Windows] 0.61.0 - Unreleased section from #571.

  • Adds ### Added, ### Changed, and ### Fixed entries grouped by theme (providers, Usage & Spend, cost, accounts, tray, serve), each with (#NNN) links following the existing section conventions.
  • Does not touch [Windows] 0.61.0 - Unreleased — that content was already reconciled by Reconcile Win-CodexBar 0.61.0 release notes #571 and remains unchanged.
  • No version bump: version.env untouched, no release section implied beyond Unreleased, no tag.

Exact changed-file set: CHANGELOG.md only (31 insertions).

Validation

Coverage notes

@coderabbitai

coderabbitai Bot commented Sep 21, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Finesssee

Copy link
Copy Markdown
Collaborator Author

Thermo-nuclear code-quality review

Verdict: FINDINGS. Reviewed head 1694651ae. The branch is behind main.

P2: This creates a second "Unreleased" release block instead of extending the existing one

CHANGELOG.md already opens with ## [Windows] 0.61.0 - Unreleased. This PR puts a new ## Unreleased above it, so the file now has two unreleased sections. A reader can't tell which release ships which change, and the release step has to reconcile both by hand. Fold these entries into the canonical unreleased section, or rename that section if these changes belong to a later version. Either way the file should keep one unreleased block, in the existing [Windows] x.y.z format.

P2: Entries duplicate what is already on main

  • The Hide Personal Info Account N fix ([0.60.4] Keep Claude account labels private #555) already appears under 0.61.0 → Fixed on main, word for word.
  • The first Added bullet repeats CodeRabbit, Muse Code and Nous Portal, which the 0.61.0 summary already lists.

When two sections describe the same change, one of them goes stale. Each change should be recorded once.

P2: The list is stale against current main

The branch predates #588 (0.63.0 dashboard spend) and #604 (0.64.0 provider adapters), and neither is listed. The fleet PRs still in flight (#596–#605, integrated through #610) will also land after this. Regenerate the list from main at merge time. If it's written this far ahead, it will be wrong again by the time it lands.

P3: Keep internal plumbing out of user-facing notes

"transient provider detail carrier", "transient provider inventory plumbing" and "Prometheus metrics endpoint with maintainable module structure" describe implementation, not behavior. Rewrite them as what the user sees, or drop them.

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