feat: add automated .NET dependency management workflow #4028
Conversation
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
## .NET Core/SDK Automated Upgrade Management - Weekly automated checking for new .NET Core/SDK releases - Intelligent global.json and project file updates with compatibility validation - Multi-version support with build verification across all .NET projects ## Key Features - ✅ **Multi-source monitoring**: Official releases API + package manager updates - ✅ **Smart compatibility**: Preserves project compatibility while upgrading dependencies - ✅ **Build validation**: Full solution build verification after .NET updates - ✅ **Version pinning**: Updates global.json SDK version with compatibility checks - ✅ **Package updates**: NuGet package upgrades with conflict resolution ## Update Strategy - **Weekly schedule**: Mondays at 8 AM for consistent .NET maintenance - **Manual triggers**: On-demand updates for critical security releases - **Graduated response**: Different handling for LTS vs current releases - **Rollback safety**: Build failures prevent PR creation ## Integration Benefits - **Release compatibility**: Ensures runner builds with latest .NET versions - **Security updates**: Automated security patch integration - **Build stability**: Validates compatibility before suggesting changes - **Development workflow**: Reduces manual .NET maintenance overhead ## Dependencies - **Requires**: Labels from actions#4024 (dependency, needs-manual-review) - **Integrates with**: Overall monitoring from actions#4025 - **Complements**: NPM security management from actions#4027 This workflow ensures .NET dependencies stay current and secure while maintaining build compatibility for the monthly runner release cycle.
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR introduces an automated .NET SDK dependency management workflow to streamline weekly .NET Core/SDK updates with intelligent compatibility validation and build verification.
Key Changes:
- Automated weekly .NET SDK updates via GitHub Actions workflow
- Smart version detection and compatibility checking
- Automated updates to global.json, devcontainer configuration, and development scripts
- Pull request creation with proper labeling for dependency tracking
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| run: | | ||
| gh pr create -B main -H feature/dotnetsdk-upgrade/${{ needs.dotnet-update.outputs.DOTNET_LATEST_MAJOR_MINOR_PATCH_VERSION }} --title "Update dotnet sdk to latest version @${{ needs.dotnet-update.outputs.DOTNET_LATEST_MAJOR_MINOR_PATCH_VERSION }}" --label "dependency" --body " |
There was a problem hiding this comment.
According to the custom coding guidelines, changes should be accompanied by non-trivial tests. This workflow lacks test coverage to verify the .NET SDK upgrade functionality works correctly.
## Schedule Optimization - **Updated time**: Monday 12 AM (midnight) → 8 AM UTC - **Reasoning**: Independent of Node.js/NPM, runs in parallel with other updates - **Position**: Third in dependency update sequence ## Optimal Monday Schedule (Option A) - 6 AM UTC: Node.js updates (foundation) - 7 AM UTC: NPM security audit (depends on Node.js) - **8 AM UTC: .NET SDK updates** ← Updated (independent) - 9 AM UTC: Docker/Buildx updates (independent) - 10 AM UTC: Dependency monitoring (summary) This timing allows .NET updates to run independently while maintaining the coordinated Monday morning dependency management approach.
TingluoHuang
approved these changes
Sep 9, 2025
fmartinez255
pushed a commit
to TiVo/actions-runner
that referenced
this pull request
Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Update labels for dotnet dependency management