Repository navigation
Bump Respawn from 6.2.1 to 7.0.0 - #225
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: Respawn dependency-version: 7.0.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/nuget/BookTracker.Tests/Respawn-7.0.0
branch
from
May 11, 2026 11:41
50a7653 to
96a6feb
Compare
N3rdage
added a commit
that referenced
this pull request
May 12, 2026
* chore(deps): upgrade bunit 1.40.0 → 2.7.2 with migration Dependabot PR #221's bump failed CI on two breaking changes between bunit 1.x and 2.x: - TestContext renamed to BunitContext (CS0618 warning in 1.x → error in 2.x with treat-warnings-as-errors elsewhere; here it'd be obsolete-with-error CS0619 either way). - RenderComponent<T>() obsoleted in favour of Render<T>() — same signature, just renamed; nine call sites in MudAuthorPickerTests. Migration applied: - ComponentTestBase now inherits BunitContext (was TestContext). - All nine RenderComponent<MudAuthorPicker>() calls become Render<MudAuthorPicker>(). Runtime surprise the compile-fix didn't reveal: MudBlazor 8.x's KeyInterceptorService and PointerEventsNoneService register as IAsyncDisposable-only. bUnit 2.x's BunitContext.Dispose() calls the ServiceProvider's sync Dispose path, which refuses async-only services: "type only implements IAsyncDisposable. Use DisposeAsync to dispose the container." All nine tests failed teardown with that error. Fix on ComponentTestBase: implement xUnit's IAsyncLifetime so the disposal goes via DisposeAsync (Task return) which casts to IAsyncDisposable and delegates to BunitContext's own DisposeAsync (ValueTask return). `new` keyword on DisposeAsync because it hides BunitContext's same-named method with a different return type — acknowledged explicit shadow, not an accidental hide. After: 9 / 9 component tests pass. * chore(deps): upgrade Respawn 6.2.1 → 7.0.0 with migration Dependabot PR #225's bump failed CI on a breaking API change: Respawner.CreateAsync(string, ...) and ResetAsync(string) overloads removed; both now require DbConnection. Migration applied in TestDbContextFactory: - Added Microsoft.Data.SqlClient using. - WipeAndReseed now opens a fresh SqlConnection per invocation and passes it to both GetRespawner + ResetAsync. Respawn builds its FK graph at CreateAsync time and doesn't hold the connection afterwards, so a per-call open/dispose is fine; no need to share a connection across the two calls. - GetRespawner signature now takes (SqlConnection) — the lazy init still races at most once (semaphore), still cached process-wide. 253 of 254 integration tests pass; 1 skipped (pre-existing, surname case-insensitivity test that documented a limitation). * chore(deps): defer Microsoft.ApplicationInsights.AspNetCore 3.x Dependabot PR #222 (2.22.0 → 3.1.1) is not a routine bump — 3.x is a full OpenTelemetry-based rewrite of the classic ApplicationInsights SDK. ITelemetryInitializer (used by UserTelemetryInitializer.cs to stamp Easy Auth user names onto telemetry items) is removed; the entire concept is replaced with OpenTelemetry processors. Migration needs a design pass over Program.cs's telemetry setup, not just a version bump. Resolution shape: - .github/dependabot.yml gains an ignore rule for major-version bumps of this specific package. Minor / patch updates within 2.x keep auto-applying. Dependabot won't keep re-opening the same failing PR every week. - TODO #42 captures the migration scope so the work isn't lost — replace UserTelemetryInitializer with BaseProcessor<Activity> reading IHttpContextAccessor, audit Program.cs's AddApplication- InsightsTelemetry call, verify codeless attach interaction. When PR #222 closes (Dependabot will skip the major-bump pattern on its next run), this loop closes.
Contributor
Author
|
Looks like Respawn is no longer updatable, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/nuget/BookTracker.Tests/Respawn-7.0.0
branch
May 12, 2026 03:43
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.
Updated Respawn from 6.2.1 to 7.0.0.
Release notes
Sourced from Respawn's releases.
7.0.0
What's Changed
Microsoft.Data.SqlClientdependency by @0xced in Remove theMicrosoft.Data.SqlClientdependency jbogard/Respawn#153New Contributors
Microsoft.Data.SqlClientdependency jbogard/Respawn#153Full Changelog: jbogard/Respawn@v6.2.1...v7.0.0
Commits viewable in compare view.