Add CI pipeline to keep .NET dependencies up to date

[Copilot]

• Create .github/workflows directory structure
• Create GitHub Actions workflow file (check-dotnet-updates.yml) that:
  • Runs on a schedule (weekly on Monday at 9:00 AM UTC)
  • Allows manual triggering via workflow_dispatch
  • Dynamically queries Microsoft's releases-index.json for supported versions
  • Only updates versions with support-phase: "active"
  • Updates CodeDependencies.iss with new versions if available
  • Updates README.md with exact versions when CI runs
  • Creates a PR with the changes
• Reverted README.md to original state (CI will update it)
• Validate workflow YAML syntax
• Run security checks (no vulnerabilities found)

Original prompt

Add CI pipeline that will keep the .net dependencies up to date.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Summary by CodeRabbit

Release Notes

• Chores
  • Implemented automated .NET dependency version checking with weekly scheduled updates and pull request workflow integration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Introduces a GitHub Actions workflow that automatically checks for .NET updates weekly and on manual trigger. Fetches release metadata, identifies newer stable versions of actively-supported .NET releases, updates CodeDependencies.iss and README.md files, and creates a pull request if updates are available.

Changes

Cohort / File(s)	Summary
GitHub Actions workflow for .NET version updates \.github/workflows/check-dotnet-updates\.yml	Adds new GitHub Actions workflow that schedules weekly checks and allows manual trigger. Fetches .NET release metadata, filters for actively-supported Core 3.x and 5+ versions, identifies newer stable releases, updates configuration and documentation with latest runtime/ASP.NET versions, and creates a pull request if updates are detected.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Verify .NET release API endpoint accuracy and response handling
• Check null/absent file handling for download URLs
• Validate patch version comparison logic across major versions
• Ensure PR creation workflow and commit message formatting are correct
• Confirm filtering logic correctly excludes legacy 1.x/2.x versions

Poem

🐰 Hop through the dotnet release feed,
Finding updates that you need!
Weekly checks keep frameworks spry,
PR created—versions fly!
Rabbit's automation hops with glee, ✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch copilot/add-ci-pipeline-dotnet-dependencies

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 1a20676 and 1ca99aa.

📒 Files selected for processing (1)

• .github/workflows/check-dotnet-updates.yml (1 hunks)

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sensslen]

@copilot make sure you keep track of the currently supported versions of .net by querying the data from microsoft, make sure to clean up the dependencies to not include out of support versions of .net. Make sure to add new .net versions as they become available. Also don't edit the readme just yet as the CI script should do so when it runs

[Copilot]

@copilot make sure you keep track of the currently supported versions of .net by querying the data from microsoft, make sure to clean up the dependencies to not include out of support versions of .net...

Updated in 1ca99aa. The workflow now:

• Dynamically queries Microsoft's releases-index.json to determine supported vs EOL versions
• Only updates versions with support-phase: "active"
• Reverted README.md to its original state - the CI will update it when versions change