Skip to content
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

(deps): Bump Buildalyzer from 3.2.2 to 3.2.8 #2969

Merged
merged 1 commit into from
Jan 22, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 20, 2022

Bumps Buildalyzer from 3.2.2 to 3.2.8.

Release notes

Sourced from Buildalyzer's releases.

3.2.8

  • Reverted UseAppHost back to defaults for Buildalyzer builds in favor of setting ComputeNETCoreBuildOutputFiles instead so that self-contained application builds still work (#194, #185, #187).
  • Added ability to bypass MSBuild when using .NET Core/.NET (I.e. the dotnet command) so that other commands like publish can be invoked (#195, thanks @​echalone).
  • Added support for analyzing build logs that don't set a TargetFrameworkMonitor (I.e. C++ projects) (#196, thanks @​echalone).

3.2.7

  • Fixed MSBuild polling in Visual Studio directories when Visual Studio 2022 is installed since it now installs into the normal "Program Files" folder (as opposed to the x86 one).

3.2.6

  • Specifies an encoding for source text in Buildalyzer.Workspaces to avoid CS8055 errors ("Cannot emit debug information for a source text without encoding") when compiling the workspace (#128).

3.2.5

  • Added a strongly-typed PreprocessorSymbols collection to AnalyzerResults and used it to flow constants through to Buildalyzer.Workspaces for .NET 5 and up projects (#191, #192, thanks @​richardwerkman).
  • Set UseAppHost to false for Buildalyzer builds since there's no need to create native executables for analysis (#185, #187, thanks @​slang25).
  • Added a test project for checking .NET 6 compatibility (#185, #186, thanks @​bernd5).

3.2.3

  • Fixed a bug where Buildalyzer.Workspaces would not add transitive references to projects in the Roslyn workspace (#181).
  • No longer attempts to add F# projects from a solution to the Roslyn workspace in Buildalyzer.Workspaces which causes an exception in Roslyn.
  • Updated structure logging support to the latest package providing binlog version 14 parsing (#184).
  • Updated Microsoft.CodeAnalysis package references in Buildalyzer.Workspaces to 3.11.0.
  • Updated MSBuild libraries for programmatic use by Buildalyzer to 16.10.0.
Changelog

Sourced from Buildalyzer's changelog.

3.2.8

  • Reverted UseAppHost back to defaults for Buildalyzer builds in favor of setting ComputeNETCoreBuildOutputFiles instead so that self-contained application builds still work (#194, #185, #187).
  • Added ability to bypass MSBuild when using .NET Core/.NET (I.e. the dotnet command) so that other commands like publish can be invoked (#195, thanks @​echalone).
  • Added support for analyzing build logs that don't set a TargetFrameworkMonitor (I.e. C++ projects) (#196, thanks @​echalone).

3.2.7

  • Fixed MSBuild polling in Visual Studio directories when Visual Studio 2022 is installed since it now installs into the normal "Program Files" folder (as opposed to the x86 one).

3.2.6

  • Specifies an encoding for source text in Buildalyzer.Workspaces to avoid CS8055 errors ("Cannot emit debug information for a source text without encoding") when compiling the workspace (#128).

3.2.5

  • Added a strongly-typed PreprocessorSymbols collection to AnalyzerResults and used it to flow constants through to Buildalyzer.Workspaces for .NET 5 and up projects (#191, #192, thanks @​richardwerkman).
  • Set UseAppHost to false for Buildalyzer builds since there's no need to create native executables for analysis (#185, #187, thanks @​slang25).
  • Added a test project for checking .NET 6 compatibility (#185, #186, thanks @​bernd5).

3.2.4

  • Updated structured logging library to consolidate MSBuild and binary logging types (internal change, should be no impact to consumers).

3.2.3

  • Fixed a bug where Buildalyzer.Workspaces would not add transitive references to projects in the Roslyn workspace (#181).
  • No longer attempts to add F# projects from a solution to the Roslyn workspace in Buildalyzer.Workspaces which causes an exception in Roslyn.
  • Updated structure logging support to the latest package providing binlog version 14 parsing (#184).
  • Updated Microsoft.CodeAnalysis package references in Buildalyzer.Workspaces to 3.11.0.
  • Updated MSBuild libraries for programmatic use by Buildalyzer to 16.10.0.
Commits
  • 4adcd95 Cleanup and release prep
  • a71b5ba Use empty string as key for project properties if TargetFrameworkMoniker isn'...
  • d1e530d Added capability to use dotnet.exe only without MSBuild.dll
  • d4170f4 Reverts the AppHost setting to default and uses ComputeNETCoreBuildOutputFile...
  • d1eca00 Added additional .NET 6 tests including a variety of exe projects
  • 096871c Fixed MSBuild polling in Visual Studio directories when Visual Studio 2022 is...
  • 325949a Sets an encoding for workspace source text (#128)
  • ba22694 Fixing up some small bugs including support for .NET 5/6 dotnet --info calls
  • 5ebe40f Ignore case when looking in _cscCommandLineArguments
  • 14e6a8c Remove submodules
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 20, 2022
@dependabot dependabot bot force-pushed the dependabot/nuget/Buildalyzer-3.2.8 branch from acb2201 to 60242d8 Compare January 21, 2022 15:45
Bumps [Buildalyzer](https://github.com/daveaglick/Buildalyzer) from 3.2.2 to 3.2.8.
- [Release notes](https://github.com/daveaglick/Buildalyzer/releases)
- [Changelog](https://github.com/daveaglick/Buildalyzer/blob/main/ReleaseNotes.md)
- [Commits](phmonte/Buildalyzer@v3.2.2...v3.2.8)

---
updated-dependencies:
- dependency-name: Buildalyzer
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@arturcic arturcic force-pushed the dependabot/nuget/Buildalyzer-3.2.8 branch from 60242d8 to f116b8a Compare January 22, 2022 14:40
@mergify mergify bot merged commit d0a673a into main Jan 22, 2022
@mergify mergify bot deleted the dependabot/nuget/Buildalyzer-3.2.8 branch January 22, 2022 15:15
@arturcic arturcic added this to the 5.x milestone Jan 24, 2022
@arturcic arturcic modified the milestones: 5.x, 5.8.2 Feb 16, 2022
@github-actions
Copy link

🎉 This issue has been resolved in version 5.8.2 🎉
The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant