-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PSA: Old versions of actions/setup-dotnet
will break soon
#2091
Comments
Those in charge of organizations may find it helpful to use this GitHub search query to quickly identify instances of this mistake across all of your repositories. (Replace If you want to audit your workflows for overly-specific version pinning in general, use this regex instead: |
FYI, Microsoft will start randomly disabling the old domains starting on February 3rd (about a week from now) in order to weed out people affected by this. Announcement here |
TL;DR: If you maintain a community package using GitHub Actions that specifies
uses: actions/[email protected]
or anything else more specific than@v4
, your workflow will break soon. Change it touses: actions/setup-dotnet@v4
to avoid breakage.Microsoft announced last week that due to the bankruptcy of their CDN partner, the download links for some .NET binaries and installers will cease working Q1 this year. This affects older versions of
actions/setup-dotnet
.The best practice for GitHub Actions workflows is to specify only the major version of your dependencies (IE:
uses: actions/setup-dotnet@v4
) unless you have a specific reason not to. This allows you to receive bug fixes and minor updates from action maintainers without any effort on your part.Unfortunately due to some copy+pasting of workflows within the Bonsai community, many of our workflows (particularly around publishing documentation) specify
uses: actions/[email protected]
, which is overly specific.If any of your workflows use specific versions, it's strongly recommended that you drop everything other than the major version number. (This applies for all actions, not just
setup-dotnet
.)The text was updated successfully, but these errors were encountered: