Skip to content

Install both test runtimes in the deploy workflow - #152

Merged
MichaelGHSeg merged 1 commit into
mainfrom
ci/deploy-runtimes
Sep 30, 2026
Merged

MichaelGHSeg merged 1 commit into
mainfrom
ci/deploy-runtimes

Conversation

@MichaelGHSeg

Copy link
Copy Markdown
Contributor

The 3.0.0 release failed in verify:

Testhost process for source(s) '.../Tests/bin/Debug/net6.0/Tests.dll' exited with error:
You must install or update .NET to run this application.
Framework: 'Microsoft.NETCore.App', version '6.0.0'
The following frameworks were found: 8.0.6, 8.0.22, 8.0.31, 9.0.6, 9.0.20, 10.0.8, 10.0.11, 10.0.12

Tests targets net10.0;net6.0. ci.yml installs both runtimes; deploy.yml still pinned 8.0.x in both of its jobs, so there was no 6.0 runtime to execute that leg. My oversight when scoping deploy.yml — I updated the SDK pin in ci.yml and not here.

Nothing was published: verify gates deploy, and NuGet is still on 2.6.0.

Re-tagging

deploy.yml runs from the tagged commit, so merging this does not change what 3.0.0 runs. The tag has to be recreated once this lands:

git push origin :refs/tags/3.0.0 && git tag -d 3.0.0
git checkout main && git pull
git tag 3.0.0 && git push origin 3.0.0

3.0.0 is unused on NuGet, so the number is free to reuse.

Tests target net10.0 and net6.0. ci.yml installs both, deploy.yml pinned 8.0.x
in both jobs, so the 3.0.0 release failed in verify: the runner offered 8, 9
and 10 but no 6.0 runtime to execute the net6.0 leg.

Nothing published — verify gates deploy.
@MichaelGHSeg
MichaelGHSeg merged commit b996cf0 into main Sep 30, 2026
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants