Docs(reports,fabric-cli): keep Fabric CLI current unless pinned; bump reports 26.24.7, fabric-cli 26.24.1

.claude-plugin/marketplace.json

@@ -5,7 +5,7 @@
   },
   "metadata": {
     "description": "A marketplace for skills and tools for agentic Power BI development.",
-    "version": "26.24.6"
+    "version": "26.24.7"
   },
   "plugins": [
     {

plugins/fabric-cli/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "fabric-cli",
-  "version": "26.24",
+  "version": "26.24.1",
   "description": "Get this plugin to work with Fabric / Power BI service, by means of the fabric cli.",
   "author": {
     "name": "Kurt Buhler",

plugins/fabric-cli/skills/fabric-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: fabric-cli
-version: 26.24
+version: 26.24.1
 description: Expert guidance for using the Fabric CLI (`fab`) to fully interact with Fabric workspaces, items, and configuration. Automatically invoke this skill whenever the user mentions "Fabric" or "Power BI Service" or a "Fabric/Power BI workspace".
 ---
 
@@ -10,7 +10,7 @@ Guidance for using `fab` to programmatically manage Fabric & Power BI service
 
 - Install via `uv tool install ms-fabric-cli` (get `uv` via `winget install uv` or `brew install uv`)
 - Fabric CLI is for working with the Cloud environment and not local files; it works with Power BI Pro, PPU, or Fabric; you DO NOT need a Fabric SKU to use the Fabric CLI
-- Keep `fab` current: `uv tool upgrade ms-fabric-cli`. Discover commands and flags with `fab --help` and `fab <command> --help` rather than hard-coding behavior; the CLI surface changes regularly
+- Keep `fab` current: check the installed version against the latest `ms-fabric-cli` release and upgrade with `uv tool upgrade ms-fabric-cli` unless the user has pinned a specific version. Discover commands and flags with `fab --help` and `fab <command> --help` rather than hard-coding behavior; the CLI surface changes regularly
 
 > [!IMPORTANT] 
 > Any time you encounter errors, user preferences or learnings when using the Fabric cli, ALWAYS note these down in the user memory rules, i.e. `.claude/rules/fabric-cli.md` for future improvement. 
@@ -24,7 +24,7 @@ Guidance for using `fab` to programmatically manage Fabric & Power BI service
 
 ## Critical general rules
 
-- IMPORTANT: The first time you use `fab` run check that it is up to date to the latest version and run `fab auth status`; If user isn't authenticated, ask them to run `fab auth login`
+- IMPORTANT: The first time you use `fab` run check that it is up to date to the latest version (upgrade with `uv tool upgrade ms-fabric-cli` unless the user has pinned a version) and run `fab auth status`; If user isn't authenticated, ask them to run `fab auth login`
 - Always use `fab --help` and `fab <command> --help` the first time you use a command to understand its syntax
 - You must search the skill /references/ for relevant reference files that explain certain commands, examples, scripts, or workflows before you start using `fab`
 - Before first use, ask the user if they have Fabric admin access, sensitivity labels or DLP policies, any API restrictions, or preferences for Fabric/Power BI API usage; remind user to add this to memory files

plugins/reports/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "reports",
-  "version": "26.24.6",
+  "version": "26.24.7",
   "description": "Get this plugin for agentic development and management of reports.",
   "author": {
     "name": "Kurt Buhler",

plugins/reports/skills/pbir-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pbir-cli
-version: 26.24.6
+version: 26.24.7
 description: This skill should be used whenever the user mentions "pbir", "pbir-cli", "Power BI reports", or "PBI reports", works with .pbir, .pbip, or .pbix files, or wants to refresh, screenshot, or visually verify a report that is open in Power BI Desktop. Covers creating, exploring, formatting, validating, and publishing Power BI reports through the pbir CLI and object model, plus driving Power BI Desktop (canvas reload, page screenshots) and querying connected or local semantic models.
 ---
 
@@ -18,6 +18,8 @@ Check the installed CLI version with `pbir --version` and compare it against the
 
 **If a command or flag documented in this skill does not exist in the installed CLI, the skill is likely ahead of the installed `pbir-cli` release.** This is especially common for the `pbir desktop` commands, which evolve quickly. Before treating a missing command as a CLI failure (and before falling back to editing JSON directly), confirm with `pbir <command> --help` and `pbir --version`, then upgrade to the latest `pbir-cli` from PyPI. Do not work around a missing newer command by hand-editing report JSON when an upgrade would provide it.
 
+When publishing to Fabric (`pbir publish`) alongside the `fabric-cli` plugin, also keep the Fabric CLI (`fab`) current — upgrade with `uv tool upgrade ms-fabric-cli` unless the user has pinned a specific version.
+
 ## Learning from Mistakes
 
 Log learnings about the `pbir` CLI in the project's memory file: gotchas, unexpected behavior, user expectations, and design preferences. Use the agent-appropriate path: