Add .NET Core 3.1 to release workflow setup-dotnet#54
Merged
Conversation
The test project targets netcoreapp3.1 but release.yaml only installed .NET 5.0+, causing testhost to fail at runtime with "You must install or update .NET to run this application." pr.yaml already installs 3.1.x; this aligns release.yaml with that. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 task
This was referenced Apr 27, 2026
Closed
Upgrade release workflow actions to Node 24 and add .NET Core 3.1
Chris-Wolfgang/ETL-Transformers#16
Merged
Merged
Upgrade release workflow actions to Node 24 and add .NET Core 3.1
Chris-Wolfgang/In-memory-Logger#34
Merged
Chris-Wolfgang
added a commit
to Chris-Wolfgang/DbContextBuilder
that referenced
this pull request
Apr 28, 2026
## Summary - `actions/download-artifact`: v4 → v8.0.1 - `softprops/action-gh-release`: v2.5.0 (SHA `a06a81a0`) → v3.0.0 (SHA `b4309332`) - Adds `3.1.x` to `dotnet-version` in all 3 `setup-dotnet` blocks. Bundles two related release-workflow fixes: 1. Node 24 actions upgrade (mirrors [ETL-Test-Kit#54](Chris-Wolfgang/ETL-Test-Kit#54)) — clears Node 20 deprecation warning. 2. .NET Core 3.1 SDK in setup-dotnet (mirrors [ETL-Json#54](Chris-Wolfgang/ETL-Json#54)) — needed because test projects target `netcoreapp3.1`. ## Breaking change review - `download-artifact` v5 changed the output path for single artifact downloads by ID. This workflow only downloads by `name:`, so unaffected. - `action-gh-release` v3.0.0 is purely a Node 24 runtime bump per release notes. ## Test plan - [ ] Next release runs without Node 20 deprecation warning - [ ] .NET Core 3.1 SDK installs and netcoreapp3.1 tests succeed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
The v0.2.0 release failed because release.yaml's
setup-dotnetstep only installs .NET 5.0+ but the test project targetsnetcoreapp3.1:Fix
Add
3.1.xtosetup-dotnetin all 3 jobs in release.yaml. This matches what pr.yaml already does (PR checks pass because they install 3.1.x; release fails because it didn't).Files changed
.github/workflows/release.yaml— 3 occurrences ofdotnet-versionupdated🤖 Generated with Claude Code