Skip to content

Bump the analyzers group with 2 updates#6

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/analyzers-972160da10
Closed

Bump the analyzers group with 2 updates#6
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/analyzers-972160da10

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 20, 2026

Updated Microsoft.CodeAnalysis.Analyzers from 3.11.0 to 5.3.0.

Release notes

Sourced from Microsoft.CodeAnalysis.Analyzers's releases.

5.0.4

Release

5.0.2

Release Notes
Install Instructions

Repos

5.0.1

Release Notes
Install Instructions

Repo

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

Commits viewable in compare view.

Updated Microsoft.CodeAnalysis.CSharp from 4.11.0 to 5.3.0.

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps Microsoft.CodeAnalysis.Analyzers from 3.11.0 to 5.3.0
Bumps Microsoft.CodeAnalysis.CSharp from 4.11.0 to 5.3.0

---
updated-dependencies:
- dependency-name: Microsoft.CodeAnalysis.Analyzers
  dependency-version: 5.3.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: analyzers
- dependency-name: Microsoft.CodeAnalysis.CSharp
  dependency-version: 5.3.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: analyzers
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 20, 2026

Labels

The following labels could not be found: dependencies, nuget. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot requested a review from jkindrix as a code owner May 20, 2026 18:31
@jkindrix
Copy link
Copy Markdown
Owner

@dependabot rebase

@jkindrix
Copy link
Copy Markdown
Owner

Closing this PR. The bundled bump of Microsoft.CodeAnalysis.CSharp 4.11.0 → 5.3.0 is incompatible with our target frameworks: 5.x ships with Roslyn 5 (.NET 10 SDK), but we target net8.0/net9.0 whose SDKs ship Roslyn 4.x. CI fails with CS9057: Analyzer assembly ... references version '5.3.0.0' of the compiler, which is newer than the currently running version '4.14.0.0'.

Splitting this into two separate bumps in follow-up commits:

  • Microsoft.CodeAnalysis.CSharp: stay on the 4.x line (probably 4.14.0 to match shipped Roslyn)
  • Microsoft.CodeAnalysis.Analyzers: bump to 5.3.0 standalone (design-time package, not compiler-version-coupled)

@jkindrix jkindrix closed this May 20, 2026
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 20, 2026

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@jkindrix jkindrix deleted the dependabot/nuget/analyzers-972160da10 branch May 20, 2026 18:46
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 20, 2026

Oh no! Something went wrong on our end. Please try again later.

If the problem persists, please contact GitHub support for assistance 🙇

jkindrix added a commit that referenced this pull request Jun 3, 2026
…I-82)

The single biggest cutover de-risk (advisor O-13 / D-11): until now NPOI<->SDK
behavioral parity was maintained by hand cross-checking, with no test running the
SAME scenario through BOTH engines. This harness does exactly that — each case
builds via the public API, round-trips (Save->Open) through Workbook.Create()/Open()
(NPOI) and Workbook.CreateOoxml()/OpenOoxml() (SDK), reads an observable projection,
and asserts the two engines agree.

Covers cell values/kinds, 1900/1904 dates, rich-text runs, cell styles, merges,
named ranges, sheet visibility/gridlines, column width/hidden, row height/hidden,
and two-cell picture anchors (FromCell/ToCell + EMU offsets).

Compared SEMANTICALLY, not byte-identical XML: the engines legitimately differ on
unset-axis materialization (NPOI resolves a cell that sets no number format to
"General" / an unsized run to FontSize 11; the SDK preserves the inherit semantic
as null — SDK-quirk #6 / lesson #10). Projections compare the axes each scenario
sets and pull those defaults out, documenting the divergence rather than hiding it.

Malformed-input parity (the silent-default-vs-fail-loud half) lands next, with the
I-83 fail-loud alignment.
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.

1 participant