Upgrade GitHub Actions workflows to v5 for checkout and setup-dotnet

[Copilot]

Summary

This PR upgrades all GitHub Actions workflows in the repository to use v5 versions of actions/checkout and actions/setup-dotnet. The upgrade ensures the repository uses the latest stable major versions of these critical actions while maintaining full backward compatibility.

Changes Made

Updated .github/workflows/dotnetcore.yml:

• actions/[email protected] → actions/checkout@v5
• actions/setup-dotnet@v4 → actions/setup-dotnet@v5 (2 occurrences)

All changes use major version tag pinning format (@v5) for consistency and automatic receipt of patch updates.

What Was Preserved

✅ All workflow functionality - No changes to build, test, or pack logic
✅ All action parameters - The dotnet-version inputs remain unchanged:

• 8.0.x
• 10.0.100-rc.1.25451.107
  ✅ All workflow configuration - Triggers (on: [push]), runner settings (windows-latest), and job configuration remain identical
  ✅ All build steps - The complete workflow logic is preserved

Validation

• ✅ YAML syntax validated successfully
• ✅ All action parameters verified as preserved
• ✅ CodeQL security scan passed with 0 alerts
• ✅ No functional changes introduced

Impact

This is a minimal, surgical change affecting only 3 lines in a single file. Only action version strings were modified - no logic, parameters, or workflow behavior changes.

Diff Summary

 .github/workflows/dotnetcore.yml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Recommendation

Monitor the initial workflow run after merging to ensure compatibility. The v5 versions are designed to be fully backward compatible with v4 configurations, and no breaking changes are expected based on GitHub's semantic versioning practices for actions.

Benefits

• Latest features: Access to the newest capabilities in GitHub Actions
• Security updates: Automatic receipt of security patches within the v5 major version
• Performance improvements: Benefit from optimizations in the latest action versions
• Future-proofing: Aligns with GitHub's recommended action versions

Original prompt

Upgrade all GitHub Actions workflows under .github/workflows/ in AzureAD/microsoft-identity-abstractions-for-dotnet so that actions/checkout and actions/setup-dotnet use major version v5. Procedure:

1. Locate each workflow YAML file.
2. Change actions/checkout@v2/@v3/@v4 (or SHA) to actions/checkout@v5.
3. Change actions/setup-dotnet@v1/@v2/@v3/@v4 (or SHA) to actions/setup-dotnet@v5 while keeping existing with: inputs unchanged.
4. Preserve all other workflow content (triggers, matrices, permissions, env vars).
5. Prefer tag pinning (@v5). If existing convention uses commit SHAs, mirror that for these actions and mention resolved SHAs in the PR body.
6. Validate YAML consistency.
   PR body should include: summary, list of modified files, assurance no functional steps changed except action versions, recommendation to monitor initial run.
   Do not modify non-workflow files.

This pull request was created as a result of the following prompt from Copilot chat.

Upgrade all GitHub Actions workflows under .github/workflows/ in AzureAD/microsoft-identity-abstractions-for-dotnet so that actions/checkout and actions/setup-dotnet use major version v5. Procedure:

1. Locate each workflow YAML file.
2. Change actions/checkout@v2/@v3/@v4 (or SHA) to actions/checkout@v5.
3. Change actions/setup-dotnet@v1/@v2/@v3/@v4 (or SHA) to actions/setup-dotnet@v5 while keeping existing with: inputs unchanged.
4. Preserve all other workflow content (triggers, matrices, permissions, env vars).
5. Prefer tag pinning (@v5). If existing convention uses commit SHAs, mirror that for these actions and mention resolved SHAs in the PR body.
6. Validate YAML consistency.
   PR body should include: summary, list of modified files, assurance no functional steps changed except action versions, recommendation to monitor initial run.
   Do not modify non-workflow files.

---

💡 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.

[jmprieur]

LGTM
thanks!