Skip to content

Fix Android SDK CI setup and suppress netcoreapp3.1 Unsafe warning - #2627

Merged
Perksey merged 1 commit into
dotnet:mainfrom
AustinAviv:fix/ci-android-sdk
Oct 11, 2026
Merged

Perksey merged 1 commit into
dotnet:mainfrom
AustinAviv:fix/ci-android-sdk

Conversation

@AustinAviv

Copy link
Copy Markdown
Contributor

Summary of the PR

Resolves CI failures across GitHub Actions workflows:

  1. Updates android-actions/setup-android to v4.0.4 in .github/workflows/build.yml and .github/workflows/sdl2.yml. Google removed the deprecated tools package from Android SDK distribution mirrors, which caused android-actions/setup-android@v2 to fail with exit code 1 during sdkmanager setup. Action version 4.0.4 replaces tools with platform-tools.

  2. Adds <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings> in build/props/common.props. System.Runtime.CompilerServices.Unsafe 6.1.2 emits a TFM compatibility warning on netcoreapp3.1, which caused BuildLibSilkDroid to fail when warnings are treated as errors. Suppressing this warning allows MSBuild to build netcoreapp3.1 targets under newer .NET SDKs.

  3. Adds <RollForward>Major</RollForward> to build/nuke/Silk.NET.NUKE.csproj so the NUKE build project executes cleanly on runners that have .NET 8+ installed.

Related issues, Discord discussions, or proposals

Related to #2622 and resolves the CI failure from run 38120826989 (job 114439401333).

Further Comments

- Update android-actions/setup-android to v4.0.4 in build.yml and sdl2.yml to avoid deprecated tools package failure

- Add SuppressTfmSupportBuildWarnings to build/props/common.props to suppress System.Runtime.CompilerServices.Unsafe warning on netcoreapp3.1

- Add RollForward Major to Silk.NET.NUKE.csproj so NUKE can execute on .NET 8+ environments
@AustinAviv

Copy link
Copy Markdown
Contributor Author

Could someone please approve the workflow for PR #2627 when you get a chance?

@Perksey

Perksey commented Oct 11, 2026

Copy link
Copy Markdown
Member

Approved.

@Perksey Perksey left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI has been going long enough that it looks like it'll pass, and the changes look good. Thank you so much!

@Perksey
Perksey enabled auto-merge (squash) October 11, 2026 15:45
@Perksey
Perksey merged commit 9ec3a1b into dotnet:main Oct 11, 2026
3 checks passed
@AustinAviv

Copy link
Copy Markdown
Contributor Author

CI has been going long enough that it looks like it'll pass, and the changes look good. Thank you so much!

It has passed, but something seems suspicious because it shouldn’t take this long

@AustinAviv

Copy link
Copy Markdown
Contributor Author

CI has been going long enough that it looks like it'll pass, and the changes look good. Thank you so much!

Thanks a lot! Really appreciate it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants