Problems with building .NET Framework 4.6.1 after overriding `v1` tag
See original GitHub issueDescription:
Context: In our project we’re using setup-dotnet
to build .NET Framework 4.6.1 console applications.
- Five days ago I made a PR and build was successful.
- I made PR today and it failed - workflow yml definition hasn’t changed - there was
actions/setup-dotnet@v1
. - I triggered
re-run
on previous PRs and they failed too (even though 5 days ago they got “green”). - I checked the releases of
setup-dotnet
and saw new one -v1.9.1
. What’s more, I observed thatv1
was updated too?
I checked that install scripts changed in the latest release and I wonder if that might be the cause of our jobs failing?
Task version:
v1
Platform:
- Ubuntu
- macOS
- Windows
Runner type:
- Hosted
- Self-hosted
Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
Expected behavior: Without changing task version, existing build started failing.
Actual behavior: Keeping the same version of task shouldn’t introduce breaking changes
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top Results From Across the Web
Known issues for the .NET Framework 4.6.1 - Microsoft Support
This article lists the known issues that you may experience after you install the Microsoft .NET Framework 4.6.1. Product issues for the .NET...
Read more >Known issues for the .NET Framework 4.6.1 RC
This article lists the known issues that you may experience after you install the Microsoft .NET Framework 4.6.1 RC.
Read more >What's new in .NET Framework - Microsoft Learn
See what's new in various versions of .NET Framework. Read a summary of key new features and improvements in each version.
Read more >Microsoft .NET Framework Repair Tool is available
The tool tries to resolve those issues by applying known fixes or by repairing corrupted installations of the supported .NET Framework versions.
Read more >Known issues when you upgrade .NET Framework from ...
Resolution · Scan Windows Update, and then install the latest .NET Framework updates that apply to .NET Framework 4.6 and 4.6.1 immediately after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That’s very good point - hm, so might it be that suddenly
windows-2022
has.NET Framework
feature turned off? 🤔EDIT: I’ve checked with
windows-2019
image and it worked like a charm!I’m closing the issue because it wasn’t related to
setup-dotnet
- sorry for bothering you @vsafonkin and thank you very much for insightful tip!Hbxbfbahss
Android için Outlookhttps://aka.ms/AAb9ysg’u edinin
From: Damian Płaza @.> Sent: Thursday, February 24, 2022 10:39:56 PM To: actions/setup-dotnet @.> Cc: Subscribed @.***> Subject: Re: [actions/setup-dotnet] Problems with building .NET Framework 4.6.1 after overriding
v1
tag (Issue #274)Closed #274https://github.com/actions/setup-dotnet/issues/274.
— Reply to this email directly, view it on GitHubhttps://github.com/actions/setup-dotnet/issues/274#event-6134556190, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AX3CQCUGGB3ZXGDC3WZMRZDU42CQZANCNFSM5PHWMP4A. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you are subscribed to this thread.Message ID: @.***>