Fix GitHub workflow configuration mismatches and add prevention guidelines

[Copilot]

Problem

GitHub workflows were not executing correctly due to configuration mismatches from the namespace rebrand (ExcelMcp → Sbroenne.ExcelMcp) and .NET version upgrade (8 → 10). While the path filters were correct, four critical configuration issues prevented workflows from building and releasing successfully.

Issues Fixed

1. .NET SDK Version Mismatch (CRITICAL)

Three workflows were configured to use .NET 8.0.x while the project requires .NET 10.0.x:

# Before
- name: Setup .NET
  uses: actions/setup-dotnet@v4
  with:
    dotnet-version: 8.0.x  # ❌ Cannot compile net10.0 projects

# After
- name: Setup .NET
  uses: actions/setup-dotnet@v4
  with:
    dotnet-version: 10.0.x  # ✅ Matches project requirements

Files affected:

• .github/workflows/release-cli.yml
• .github/workflows/codeql.yml
• .github/workflows/publish-nuget.yml

Impact: Build workflows would fail immediately with SDK version errors since .NET 8 SDK cannot compile projects targeting net10.0.

2. Incorrect Executable Name in Build Verification

The MCP Server build workflow was checking for the wrong executable name:

# Before
if (Test-Path "src/ExcelMcp.McpServer/bin/Release/net10.0/ExcelMcp.McpServer.exe")

# After  
if (Test-Path "src/ExcelMcp.McpServer/bin/Release/net10.0/Sbroenne.ExcelMcp.McpServer.exe")

File affected: .github/workflows/build-mcp-server.yml

Impact: Build verification would always fail even when builds succeeded, creating false negatives.

3. Wrong NuGet Package Name References

Package operations used the old package ID instead of the rebranded name:

# Before
ExcelMcp.McpServer.$version.nupkg
dotnet tool install --global ExcelMcp.McpServer

# After
Sbroenne.ExcelMcp.McpServer.$version.nupkg
dotnet tool install --global Sbroenne.ExcelMcp.McpServer

Files affected:

• .github/workflows/publish-nuget.yml (5 references)
• .github/workflows/release-mcp-server.yml (3 references)

Impact: Package verification and publish steps would fail, and users would receive incorrect installation instructions.

4. Outdated Runtime Requirements in Documentation

Release notes claimed ".NET 8.0 runtime" while the project actually requires ".NET 10.0 runtime":

# Before
$releaseNotes += "- .NET 8.0 runtime`n"

# After
$releaseNotes += "- .NET 10.0 runtime`n"

Files affected:

• .github/workflows/release-cli.yml (2 locations)
• .github/workflows/release-mcp-server.yml (2 locations)

Impact: Users would install the wrong runtime version and experience installation failures.

5. Prevention Guidelines Added

Added comprehensive GitHub Workflows Configuration Management section to .github/copilot-instructions.md to prevent similar issues in the future:

• Configuration Change Checklist: Lists all workflow files to check when changing .NET versions, assembly names, package IDs, or runtime requirements
• Automated Validation Script Template: PowerShell script to detect mismatches between project files and workflows
• Common Mistakes Guide: Clear guidelines on what to avoid and what to always do
• CI/CD Integration Template: Example workflow for automated configuration validation
• PR Checklist Template: Standardized checklist for configuration changes

These guidelines ensure workflows stay synchronized with project configuration during future upgrades or rebranding efforts.

Root Cause

The project underwent two major changes:

1. Namespace rebrand: ExcelMcp → Sbroenne.ExcelMcp
2. .NET version upgrade: 8 → 10

While the codebase (.csproj files, Assembly names, Package IDs) was fully updated, the CI/CD workflow configurations were not completely synchronized with these changes.

Changes Summary

• Files modified: 6 files (5 GitHub workflow files + 1 copilot-instructions.md)
• Lines changed: 34 workflow fixes + 236 lines of prevention guidelines
• Critical fixes: 4 major configuration issues + prevention measures

Verification

✅ All workflows now use .NET 10.0.x SDK
✅ Executable name matches csproj AssemblyName (Sbroenne.ExcelMcp.McpServer)
✅ Package name matches csproj PackageId (Sbroenne.ExcelMcp.McpServer)
✅ Runtime requirements correctly state .NET 10.0
✅ Path filters verified correct (were never the issue)
✅ Prevention guidelines added to copilot-instructions.md

Expected Results

After merging, workflows will:

• Build successfully with the correct .NET 10 SDK
• Find and verify correct executable files
• Create packages with correct names
• Publish to NuGet successfully with proper package IDs
• Generate accurate installation documentation
• Fire correctly on code changes to monitored paths

Plus: Future configuration changes will have clear guidelines and validation scripts to prevent similar synchronization issues.

Testing Recommendations

1. Merge this PR to enable the fixed workflows
2. Make a test commit to trigger build workflows
3. Monitor workflow execution in the GitHub Actions tab
4. Verify build artifacts use correct naming conventions
5. Use the new validation script template when making future configuration changes

Created from VS Code via the GitHub Pull Request extension.

Original prompt

please review alll my github workflows - i think they are using the wrong paths and this is why they do not fire

[Chronological Review: The conversation began with the user requesting to rename the project to "ExcelMcp.CLI" and update all documentation accordingly. The user then asked to ensure that the README focused on the MCP server, with CLI details in a separate file. The user expressed a desire to have different build and release processes for the MCP Server and CLI, and to split installation instructions accordingly. The user later specified a preference for using a specific approach for the MCP Server, including prerequisites for .NET 10 SDK and installation via winget. The user requested direct updates to files, avoiding the use of Get-ChildItem, and raised a question about naming conventions for solutions and namespaces. The user noted that some documentation was out of date and requested a review of the project for outdated links and installation instructions. The conversation continued with the user reporting build errors and requesting the addition of XML documentation. The user then asked for a review of GitHub workflows, suspecting incorrect paths were causing them not to fire.]

[Intent Mapping:

1. "Rename this project to ExcelMcp.CLI since it is a cli and update all the docs."
2. "Make sure that this readme focuses on the Mcp server. You should mention the CLI but that should be in its own file."
3. "I want our MCP Server to use this approach... We need to change to .NET 10 SDK as a prereq."
4. "Please update the files directly."
5. "Also don't use Get-ChildItem - modify it directly."
6. "Shouldn't my Solution and namespace not be prefixed with my company name 'Sbroenne'?"
7. "Please review the project - I still see links to the old GitHub projects for examples."
8. "There are build errors."
9. "No. Just add the XML documentation."
10. "Please review all my GitHub workflows - I think they are using the wrong paths and this is why they do not fire."]

[Technical Inventory:

• Technologies: .NET 10 SDK, GitHub Actions for workflows.
• Documentation: COMMANDS.md, CLI.md, RELEASE-STRATEGY.md, INSTALLATION.md, DEVELOPMENT.md, SECURITY.md, CONTRIBUTING.md.
• Workflows: build-mcp-server.yml, with a focus on separating build processes for MCP Server and CLI.]

[Code Archaeology:

• Files discussed:
  • d:\source\mcp-server-excel.github\workflows\build-mcp-server.yml
  • d:\source\mcp-server-excel\docs\COMMANDS.md
  • d:\source\mcp-server-excel\docs\RELEASE-STRATEGY.md
  • d:\source\mcp-server-excel\src\ExcelMcp.CLI\ExcelMcp.CLI.csproj
  • d:\source\mcp-server-excel\src\ExcelMcp.McpServer\ExcelMcp.McpServer.csproj
  • d:\source\mcp-server-excel\src\ExcelMcp.Core\ExcelMcp.Core.csproj
  • d:\source\mcp-server-excel\src\ExcelMcp.CLI\Program.cs]

[Progress Assessment:

• Completed Tasks: Initial project renaming and documentation updates requested.
• Partially Complete Work: Ongoing adjustments to workflows and documentation based on user feedback.
• Validated Outcomes: User has confirmed some documentation updates but noted discrepancies and build errors.]

[Context Validation: All critical information for continuation is captured, including user requests for documentation updates, project renaming, and workflow adjustments.]

[Recent Commands Analysis:

• Last Agent Commands: User requested to review GitHub workflows for incorrect paths.
• Tool Results Summary: No specific tool results were returned as the user was actively discussing issues rather than executing commands.
• Pre-Summary State: The agent was actively working on the build-mcp-server.yml file and addressing user requests regarding project structure and documentation.
• Operation Context: The user is focused on ensuring that the project adheres to best practices and resolves build issues, which connects to their overall goal of refining the MCP Server and CLI project.]

1. Conversation Overview: - Primary Objectives: The user aims to rename the project to "ExcelMcp.CLI," update documentation, ensure proper build and release processes for MCP Server and CLI, and address build errors. - Session Context: The conversation has evolved from initial renaming requests to detailed discussions about documentation, workflows, and best practices. - User Intent Evolution: The user has shifted from broad project renaming to specific concerns about documentation accuracy, build processes, and adherence to naming conventions.

2. Technical Foundation:

• .NET 10 SDK: Required as a prerequisite for the MCP Server.
• GitHub Actions: Used for CI/CD workflows, with a focus on separating processes for MCP Server and CLI.

3. Codebase Status:

• d:\source\mcp-server-excel.github\workflows\build-mcp-server.yml:
  • Purpose: Defines the build process for the MCP Server.
  • Current State: Needs review for path correctness and separation of build processes.
• d:\source\mcp-server-excel\docs\COMMANDS.md:
  • Purpose: Contain...

Created from VS Code via the GitHub Pull Request extension.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[sbroenne]

@copilot can you update your coding instructions to make sure this never happens again

[Copilot]

@copilot can you update your coding instructions to make sure this never happens again

Updated .github/copilot-instructions.md with comprehensive GitHub Workflows Configuration Management guidelines (commit 76a9cf0).

The new section includes:

• Configuration change checklist covering .NET versions, assembly names, package IDs, and runtime docs
• Automated validation script template to detect workflow/project mismatches
• Common mistakes guide and best practices
• CI/CD integration template for workflow validation
• PR checklist template for configuration changes

This ensures workflows stay synchronized with project configuration during future upgrades or rebranding efforts.