Release: v2.10.0#930
Merged
erikdarlingdata merged 1 commit intodevfrom May 4, 2026
Merged
Conversation
Bug-fix release covering #916 (Memory tab tooltip survives tab switch in Dashboard + Lite, with same popup-wedge fix extended to CorrelatedCrosshairManager) and #917 (FinOps memory recommendation now bases sizing on a 7-day P95 instead of a single snapshot in both apps). Also adds README documentation for per-database EXECUTE grants required by FinOps Index Analysis (#915). No schema changes since v2.9.0 — no upgrade folder needed. Co-Authored-By: Claude Opus 4.7 (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.
Summary
What's in 2.10.0
CorrelatedCrosshairManagerEXECUTEgrants required for FinOps Index AnalysisValidation
dotnet build -c Debug— 0 errorsInstaller.Tests— 46/46 passinginstallation_historyshows UPGRADE 2.9.0→2.10.0 SUCCESS, then REINSTALL 2.10.0→2.10.0 SUCCESScollection_loglast hour: 1164 SUCCESS, 13 NO_RESULTS, 4 SKIPPED, 0 ERRORTest plan
After this lands in dev, follow-up PR dev → main, then tag v2.10.0 and create the GitHub Release to trigger the build workflow.
🤖 Generated with Claude Code