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.

Sign up for GitHub

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

Jump to bottom

Update dotnet monorepo #144

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dotnet monorepo #144

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 10, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
Microsoft.Extensions.Caching.Abstractions (source) 2.0.0 -> 2.2.0 age adoption passing confidence nuget minor
Microsoft.Extensions.Caching.Memory (source) 2.0.0 -> 2.2.0 age adoption passing confidence nuget minor
Microsoft.Extensions.Caching.SqlServer (source) 2.0.0 -> 2.2.0 age adoption passing confidence nuget minor
Microsoft.Extensions.Caching.StackExchangeRedis (source) 2.2.0 -> 2.2.5 age adoption passing confidence nuget patch
System.Runtime.Caching (source) 4.5.0 -> 4.7.0 age adoption passing confidence nuget minor
dotnet-sdk 8.0.100 -> 8.0.404 age adoption passing confidence dotnet-sdk patch

Release Notes

dotnet/aspnetcore (Microsoft.Extensions.Caching.SqlServer)

v2.2.0

Compare Source

ASP.NET Core release notes

We have disabled view recompilation when .cshtml change by default (except for the Development environment). A new flag called AllowRecompilingViewsOnFileChange has been introduced in RazorViewEngineOptions, which can be used to configure whether the view engine will watch for file changes. The settings is set to false by default for all environments but Development. If you are using Visual Studio to debug, then it will launch the application in the Development environment by default. You can find more details about the change by looking at this PR: https://github.com/aspnet/Mvc/pull/8369/files

In case you would like to keep the view recompilation enabled for your project, you can choose so by configure Razor options in Startup.ConfigureService method using the following code block:

services.AddMvc()
    .SetCompatibilityVersion(CompatibilityVersion.Version_2_2)
    .AddRazorOptions(options => options.AllowRecompilingViewsOnFileChange = true);

Repos

v2.1.2

Compare Source

ASP.NET Core 2.1.2 Release Notes

This update includes two security fixes. Please see the following links for details.

v2.1.1

Compare Source

ASP.NET Core 2.1.1 Release Notes

We are pleased to announce the release of ASP.NET Core 2.1.1.

v2.1.0

Compare Source

ASP.NET Core 2.1.0 Release Notes

We are pleased to announce the release of ASP.NET Core 2.1.0.

Known Issues

  • Warning when building new ASP.NET Core project that targets .NET Framework
    Building a new ASP.NET Core project that targets net461 produces the following warning:

    There was a mismatch between the processor architecture of the project being built "x86" and the processor architecture of the reference "c:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.mvc.razor.viewcompilation\2.1.0-rtm-30796\build\netstandard2.0\Microsoft.AspNetCore.Mvc.Razor.ViewCompilation-x64.exe", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project

    Workaround: Remove the reference to the Microsoft.AspNetCore.Mvc.Razor.ViewCompilation package.

  • Windows authentication is not enabled after creating project with the Windows authentication option selected
    When creating a template with Windows authentication, the settings to enable Windows authentication in launchSettings.json are not applied.
    Workaround: Modify launchSettings.json as follows:

    "windowsAuthentication": true,
"anonymousAuthentication": false,

  • NullReferenceException when using a custom IAuthorizationPolicyProvider and AllowCombiningAuthorizeFilters is set to true
    Using a custom IAuthorizationPolicyProvider and setting AllowCombiningAuthorizeFilters to true causes a NullReferenceException.
    Workaround: Disable AllowCombiningAuthorizeFilters or use a single AuthorizeFilter

  • XmlSerializerOutputFormatter throws InvalidCastException for async action methods
    Invoking an Async action method may result in an InvalidCastException when using the XmlSerializerOutputFormatter.
    Workaround: Wrap the return type in ActionResult<T>. Ex. replace the return type Task<IEnumerable<string>> with Task<ActionResult<IEnumerable<String>>>.

v2.0.2

Compare Source

v2.0.1

Compare Source

dotnet/sdk (dotnet-sdk)

v8.0.404: .NET 8.0.11

Compare Source

Release

What's Changed

Full Changelog: dotnet/sdk@v8.0.403...v8.0.404

v8.0.403

Compare Source

v8.0.402

Compare Source

v8.0.401

Compare Source

v8.0.400: .NET 8.0.8

Compare Source

Release

v8.0.307

Compare Source

v8.0.306

Compare Source

v8.0.304

Compare Source

v8.0.303: .NET 8.0.7

Compare Source

Release

v8.0.302

Compare Source

v8.0.301

Compare Source

v8.0.300: .NET 8.0.5

Compare Source

Release

v8.0.206

Compare Source

v8.0.205

Compare Source

v8.0.204: .NET 8.0.4

Compare Source

Release

v8.0.203

Compare Source

v8.0.202: .NET 8.0.3

Release

v8.0.200: .NET 8.0.2

Compare Source

Release

v8.0.111

Compare Source

v8.0.110

Compare Source

v8.0.108

Compare Source

v8.0.107

Compare Source

v8.0.106: .NET 8.0.6

Compare Source

Release

v8.0.105

Compare Source

v8.0.104: .NET 8.0.4

Compare Source

Release

v8.0.103

Compare Source

v8.0.102

Compare Source

v8.0.101: .NET 8.0.1

Compare Source

Release

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/dotnet-monorepo branch from 049ac8b to f627379 Compare April 10, 2024 13:18
@renovate renovate bot force-pushed the renovate/dotnet-monorepo branch 3 times, most recently from 4d9d3c6 to dfed154 Compare May 24, 2024 20:08
@renovate renovate bot force-pushed the renovate/dotnet-monorepo branch from dfed154 to 935b88a Compare May 29, 2024 23:24
@renovate renovate bot force-pushed the renovate/dotnet-monorepo branch from 935b88a to 346139a Compare June 11, 2024 22:52
@renovate renovate bot force-pushed the renovate/dotnet-monorepo branch from 346139a to d3442f2 Compare July 10, 2024 01:22
@renovate renovate bot force-pushed the renovate/dotnet-monorepo branch 2 times, most recently from 35678aa to 921422b Compare August 16, 2024 07:58
@renovate renovate bot force-pushed the renovate/dotnet-monorepo branch from 921422b to e4d0561 Compare September 25, 2024 14:49
@renovate renovate bot force-pushed the renovate/dotnet-monorepo branch from e4d0561 to 5c3d10d Compare October 9, 2024 12:59
@renovate renovate bot force-pushed the renovate/dotnet-monorepo branch from 5c3d10d to f4cae10 Compare November 13, 2024 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants