Bump Microsoft.CodeAnalysis.BannedApiAnalyzers from 3.3.4 to 4.14.0#11562
Merged
Conversation
--- updated-dependencies: - dependency-name: Microsoft.CodeAnalysis.BannedApiAnalyzers dependency-version: 4.14.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
dependabot
Bot
requested review from
jonathanpeppers and
simonrozsival
as code owners
dependabot
Bot
added
dependencies
jonathanpeppers
approved these changes
Jun 3, 2026
jonathanpeppers
deleted the
dependabot/nuget/build-tools/banned-apis/release/10.0.1xx/Microsoft.CodeAnalysis.BannedApiAnalyzers-4.14.0
branch
jonathanpeppers
pushed a commit
to jonathanpeppers/xamarin-android
that referenced
this pull request
Jun 3, 2026
…otnet#11562) --- updated-dependencies: - dependency-name: Microsoft.CodeAnalysis.BannedApiAnalyzers dependency-version: 4.14.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
simonrozsival
added a commit
that referenced
this pull request
Jun 3, 2026
The dependabot bump (#11562) committed banned-apis.targets with CRLF bytes stored directly in the git blob. Since .gitattributes declares `*.targets eol=crlf`, the blob must be stored normalized (LF) and only converted to CRLF on checkout. The un-normalized blob caused the CI 'Ensure no modified/untracked files' check to fail because git's renormalization detection flagged the file as modified. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jonathanpeppers
added a commit
that referenced
this pull request
Jun 8, 2026
….400 SDK (#11579) PRs targeting `release/10.0.1xx` were failing in two CI steps after PR #11550 bumped the SDK to `10.0.400-preview.0.26281.104`. This PR fixes both. ## 1. `ConfigureLocalWorkload` target **Symptom** (example failing builds: [14272822](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=14272822&view=logs&j=67c36b7f-840a-5272-a1e2-d24133c10cf7&t=67453bd5-dba0-530a-0c1e-8cde57517c28&l=299), [14286661](https://devdiv.visualstudio.com/DevDiv/DevDiv%20Team/_build/results?buildId=14286661&view=logs&j=cac0e8d3-0ef5-5d2b-b57e-e8fde7204df3&t=1613c12f-4a8c-569b-7239-df554c009fc1&l=300)): ``` Workload installation failed: Workload ID android-deps is not recognized. ``` **Root cause:** `SdkDirectoryWorkloadManifestProvider` discovers loose manifests under `<root>/<SdkFeatureBand.ToString()>/`. For SDK `10.0.400-preview.0.26281.104` that string is `10.0.400-preview.0`, not `10.0.400`. The synthetic `android-deps` workload manifest was being written to `bin/Release/lib/sdk-manifests/10.0.400/android.deps.workload/...`, so the SDK's resolver never found it. Previous stable / `-rtm` / `-dev` SDKs returned just `10.0.400` from `SdkFeatureBand.ToString()`, which is why this worked before #11550. **Fix in `build-tools/create-packs/ConfigureLocalWorkload.targets`:** - Place the synthetic `android.deps.workload` folder under `$(DotNetPreviewVersionBand)` (e.g. `10.0.400-preview.0`) instead of `$(DotNetSdkManifestsFolder)` (`10.0.400`). `DotNetPreviewVersionBand` already matches `SdkFeatureBand.ToString()` for both stable and preview SDKs. - Also (defensive): run `dotnet workload config --update-mode manifests` before the install to ensure the local SDK is in loose-manifest mode, since workload-set mode is now the default in 10.0.400. `_LocalAndroidManifestFolder` is intentionally left under `$(DotNetSdkManifestsFolder)` — it is only the packaging source for the workload-manifest NuGet, not a path the SDK reads at install time. ## 2. "Ensure no modified/untracked files" dirty-tree check **Symptom** (example failing build: [14283875](https://devdiv.visualstudio.com/DevDiv/DevDiv%20Team/_build/results?buildId=14283875&view=logs&j=96fd57f5-f69e-53c7-3d47-f67e6cf9b93e&t=81b9bc1a-74a9-50ea-e57c-169f5aa3474c&l=16)): the dirty-tree check reported `build-tools/banned-apis/banned-apis.targets` and `src/Mono.Android/Mono.Android.csproj` as modified. **Root cause:** dependabot bumps (#11562, #11563) stored these files with CRLF directly in the git index. `.gitattributes` declares `*.targets` and `*.csproj` as `eol=crlf`, which means the index should hold LF and the smudge filter writes CRLF to the working tree on checkout. When CRLF is stored in the index, any cross-platform tool that touches the file causes `git status` to report changes. **Fix:** ran `git add --renormalize` on just those two files. The diff is whitespace-only (verifiable with `git diff -w`); content is unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Updated Microsoft.CodeAnalysis.BannedApiAnalyzers from 3.3.4 to 4.14.0.
Release notes
Sourced from Microsoft.CodeAnalysis.BannedApiAnalyzers's releases.
4.2.0-4.22266.5
Release
4.2.0-3.22151.16
Release
4.2.0-1.22108.11
Release
4.0.0-2.21354.7
Release
4.0.0-2.21254.26
Release
4.0.0-1.21277.15
Release
3.10.0-3.21201.20
Release
3.10.0-2.21153.36
Release
3.10.0-1.21102.26
Release
3.7.0-3.20312.3
Release Notes
Install Instructions
Repos
3.7.0-3.20269.11
Release Notes
Install Instructions
Repos
3.7.0-2.20277.1
Release Notes
Install Instructions
Repos
3.6.0
Release Notes
Install Instructions
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)