Bump dotnet/aspnet from 8.0 to 10.0 - #117
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
dependabot
Bot
added
dependencies
MusaMisto
added a commit
that referenced
this pull request
Aug 31, 2026
…127) The Docker build has failed on every run since the projects moved to net8.0 (d48988f, 2026-02-12). The Dockerfile still pinned the .NET 6 base images it was given in 2024-03-31, so the SDK 6 image could not build a net8.0 project: error NETSDK1045: The current .NET SDK does not support targeting .NET 8.0. [/src/SW.Mtm.Web/SW.Mtm.Web.csproj] That is why no chart or image has been published since 6.0.9 (Feb 2026) — `ci` fails, so `deploy` and `tag` never run. Reproduced locally byte-for-byte against the CI log before changing anything. - Dockerfile: aspnet 6.0 -> 8.0, sdk 6.0 -> 8.0 (match TargetFramework). - Dockerfile: copy SW.Mtm.MsSql.csproj into the pre-restore layer. It is a ProjectReference of SW.Mtm.Web but was never copied, so restore logged "Skipping project ... because it was not found" and the layer resolved an incomplete graph. Now 0 skip warnings. - ci-cd.yml: dotnet-version 6.0.x -> 8.0.x. Currently masked — there is no global.json, so the runner's newest preinstalled SDK is selected and the nuget job passes anyway — but the pin contradicts the projects and would break the moment a global.json is added. NOT bumping to 9.0 (Dependabot #117/#118). Verified empirically: sdk:9.0 + aspnet:9.0 BUILDS successfully and then fails at startup with "You must install or update .NET to run this application. Framework: 'Microsoft.NETCore.App', version '8.0.0'" — .NET roll-forward does not cross major versions by default. Those PRs would ship a green build and a crash-looping image. They should be closed, or the projects retargeted to net9.0 first. Verified: build fails before / succeeds after; the resulting image starts under the .NET 8 runtime and reaches application code (it then fails only on database connectivity, with no database configured locally). Claude-Session: https://claude.ai/code/session_01VHkpqv6dB6wjALyFe9ocMU Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/docker/main/dotnet/aspnet-9.0
branch
from
August 31, 2026 11:37
d8c6098 to
72d6c55
Compare
MusaMisto
added a commit
that referenced
this pull request
Aug 31, 2026
…ine (#129) The 8.0.1 image CrashLoopBackOffs at startup: System.TypeLoadException: Could not load type 'Microsoft.EntityFrameworkCore.Storage.IRelationalValueBufferFactoryFactory' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=8.0.24.0' That type was removed in EF Core 7. The projects moved to net8.0 in d48988f (2026-02-12) and most of the EF stack came with them — Design 8.0.24, Pomelo 8.0.3, EFCore.NamingConventions 8.0.3 — but two providers were left on the EF Core 5 line and call into an API that no longer exists: SW.Mtm.PgSql Npgsql.EntityFrameworkCore.PostgreSQL 5.0.10 -> 8.0.11 SW.Mtm.MsSql Microsoft.EntityFrameworkCore.SqlServer 5.0.11 -> 8.0.24 SqlServer is pinned to 8.0.24 so it matches the already-pinned Microsoft.EntityFrameworkCore.Design and keeps Relational on one patch level. Npgsql 8.0.11 is the newest 8.0.x. This blocked every deployment, not just playground: all six live releases (funride, kwickbox, tamweelna x staging/production) run dbType=PgSql. They are unaffected today only because they still run the 6.0.8 image, which predates the net8.0 migration. NOT taking Dependabot #110 (Npgsql -> 9.0.4) or #111 (Pomelo -> 9.0.0): both are EF Core 9 against an EF Core 8 app, the same major-version mismatch as #117/#118. Verified against a real PostgreSQL 16 container, same env for both images: ghcr.io/simplify9/mtm:8.0.1 -> TypeLoadException, process dies this build -> migrations run, 9 tables created in the mtm schema incl. _ef_migrations_history, app serves HTTP, zero errors in the log Unit tests pass (1/1) under the dotnet/sdk:8.0 image. Claude-Session: https://claude.ai/code/session_01VHkpqv6dB6wjALyFe9ocMU Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Bumps dotnet/aspnet from 8.0 to 10.0. --- updated-dependencies: - dependency-name: dotnet/aspnet dependency-version: '9.0' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/docker/main/dotnet/aspnet-9.0
branch
from
August 31, 2026 12:40
72d6c55 to
b356c74
Compare
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
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.
Warning
Cooldown could not be applied because no publication date was available from the registry.
Bumps dotnet/aspnet from 8.0 to 10.0.