Bump the analyzers group with 2 updates - #176
Merged
Merged
Conversation
Bumps G-Research.FSharp.Analyzers from 0.22.0 to 0.23.0 Bumps Ionide.Analyzers from 0.15.0 to 0.16.0 --- updated-dependencies: - dependency-name: G-Research.FSharp.Analyzers dependency-version: 0.23.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: analyzers - dependency-name: G-Research.FSharp.Analyzers dependency-version: 0.23.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: analyzers - dependency-name: Ionide.Analyzers dependency-version: 0.16.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: analyzers - dependency-name: Ionide.Analyzers dependency-version: 0.16.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: analyzers ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Neftedollar
added a commit
that referenced
this pull request
Aug 15, 2026
Dependabot's first run hit its default open-pull-requests-limit of 5 per ecosystem exactly (nuget: #176-#180, actions: #172-#175/#181), so anything past the cap was never proposed. dotnet list package --outdated found four real updates behind it; the limit is raised to 15 so a cap never again reads as 'nothing outdated'. Bumped: - Nerdbank.MessagePack 1.2.30 -> 1.2.36 - Microsoft.NET.Test.Sdk 17.12.0 -> 18.9.0 - xunit.runner.visualstudio 3.0.2 -> 4.0.0 - fsharp-analyzers runtime tool 0.36.0 -> 0.37.2 (dotnet-tools.json and the ProjectHealth constant move together; they are two copies of one pin) Deliberately NOT bumped: Microsoft.VisualStudio.Threading.Only stays at 17.14.15. StreamJsonRpc 2.25.29 is the latest release and its lock entry requires exactly 17.14.15; the pin exists because fresh host processes otherwise fail set_project with FileNotFoundException for Microsoft.VisualStudio.Threading 17.14.0.0 (#121). Also fixes drift the grouped analyzer bump left behind: fcs_analyzer_setup_preview emitted paste-ready snippets recommending G-Research 0.22.*/Ionide 0.15.* while the project files had already moved to 0.23.0/0.16.0. No test bound the two, so nothing caught it. Verified on SDK 10.0.400: locked restore clean, build 0 warnings/0 errors, full suite 549/549, and a live stdio probe (set_project against this repo) returns workspaceLoadStatus=ready with the LSP started — the #121 bind holds. Co-authored-by: Roman Melnikov <roman@neftedollar.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 G-Research.FSharp.Analyzers from 0.22.0 to 0.23.0.
Release notes
Sourced from G-Research.FSharp.Analyzers's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Ionide.Analyzers from 0.15.0 to 0.16.0.
Release notes
Sourced from Ionide.Analyzers's releases.
No release notes found for this version range.
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 <dependency name> major versionwill 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 versionwill 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