Repository navigation
chore: Bump HotChocolate.Data from 15.1.11 to 15.1.12 - #10
dependabot[bot] wants to merge 3 commits into
Conversation
--- updated-dependencies: - dependency-name: HotChocolate.Data dependency-version: 15.1.12 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
NuGet Package Updates: - FastEndpoints: 7.1.1 -> 7.2.0 - FastEndpoints.Swagger: 7.1.1 -> 7.2.0 - HotChocolate.AspNetCore: 15.1.11 -> 15.1.12 - HotChocolate.Data: 15.1.11 -> 15.1.12 - Microsoft.AspNetCore.OpenApi: 10.0.1 -> 10.0.2 - Microsoft.Data.SqlClient: 6.1.3 -> 6.1.4 - Microsoft.Data.Sqlite: 10.0.1 -> 10.0.2 - Microsoft.EntityFrameworkCore: 10.0.1 -> 10.0.2 - Microsoft.EntityFrameworkCore.InMemory: 10.0.1 -> 10.0.2 - Microsoft.EntityFrameworkCore.Relational: 10.0.1 -> 10.0.2 - Microsoft.EntityFrameworkCore.Tasks: 10.0.1 -> 10.0.2 - Microsoft.AspNetCore.Mvc.Testing: 10.0.0-rc.2.25502.107 -> 10.0.2 GitHub Actions Updates: - actions/checkout: v4.2.2 -> v6.0.1 - actions/setup-dotnet: v4.3.1 -> v5.1.0 - actions/upload-artifact: v4.6.2 -> v6.0.0 - codecov/codecov-action: af2ee03 -> 671740a - dawidd6/action-download-artifact: v7 -> v12 Closes #2, #3, #4, #5, #6, #8, #9, #10, #11, #12, #13, #14, #16, #17
|
Closed in favor of combined PR #24 |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
* chore: Combined Dependabot updates - NuGet packages and GitHub Actions NuGet Package Updates: - FastEndpoints: 7.1.1 -> 7.2.0 - FastEndpoints.Swagger: 7.1.1 -> 7.2.0 - HotChocolate.AspNetCore: 15.1.11 -> 15.1.12 - HotChocolate.Data: 15.1.11 -> 15.1.12 - Microsoft.AspNetCore.OpenApi: 10.0.1 -> 10.0.2 - Microsoft.Data.SqlClient: 6.1.3 -> 6.1.4 - Microsoft.Data.Sqlite: 10.0.1 -> 10.0.2 - Microsoft.EntityFrameworkCore: 10.0.1 -> 10.0.2 - Microsoft.EntityFrameworkCore.InMemory: 10.0.1 -> 10.0.2 - Microsoft.EntityFrameworkCore.Relational: 10.0.1 -> 10.0.2 - Microsoft.EntityFrameworkCore.Tasks: 10.0.1 -> 10.0.2 - Microsoft.AspNetCore.Mvc.Testing: 10.0.0-rc.2.25502.107 -> 10.0.2 GitHub Actions Updates: - actions/checkout: v4.2.2 -> v6.0.1 - actions/setup-dotnet: v4.3.1 -> v5.1.0 - actions/upload-artifact: v4.6.2 -> v6.0.0 - codecov/codecov-action: af2ee03 -> 671740a - dawidd6/action-download-artifact: v7 -> v12 Closes #2, #3, #4, #5, #6, #8, #9, #10, #11, #12, #13, #14, #16, #17 * fix: Correct GitHub Actions SHAs for v6.0.1 and v6.0.0 - actions/checkout@v6.0.1: 8e8c483db84b4bee98b60c0593521ed34d9990e8 - actions/upload-artifact@v6.0.0: b7c566a772e6b6bfb58ed0dc250532a479d7789f * fix: Correct setup-dotnet SHA for v5.1.0 - actions/setup-dotnet@v5.1.0: baa11fbfe1d6520db94683bd5c7a3818018e4309 * Fix race condition in Azure Service Bus integration test perspective waiter Root Cause: CountingPerspectiveReceptor used ConcurrentBag with Contains() + Add() pattern, which is NOT atomic. Under concurrent execution, multiple threads could pass the Contains() check before any Add() completes, resulting in duplicate counting or missed counts, causing tests to timeout or complete prematurely. Race Condition Example: 1. Thread A: !Contains(key) → true 2. Thread B: !Contains(key) → true (before A adds) 3. Thread A: Add(key), Increment(count) // count = 1 4. Thread B: Add(key), Increment(count) // count = 2 (DUPLICATE!) 5. Result: Same perspective counted twice OR waiter never reaches expected count Fix: - Replace ConcurrentBag<string> with ConcurrentDictionary<string, byte> - Replace Contains() + Add() with atomic TryAdd() - TryAdd() returns true only for first caller, preventing race Files Changed: - CountingPerspectiveReceptor.cs: Use ConcurrentDictionary + TryAdd() - PerspectiveCompletionWaiter.cs: Create ConcurrentDictionary instead of ConcurrentBag - ServiceBusIntegrationFixture.cs: Same fix for WaitForPerspectiveCompletionAsync This explains why RabbitMQ tests aren't flaky - they use PerspectiveCompletionWaiter from TestUtilities which now has the fix, while Service Bus tests had duplicate code. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Fix InMemory integration test fixture to use ConcurrentDictionary Missed updating InMemoryIntegrationFixture when fixing the race condition in CountingPerspectiveReceptor. Changed ConcurrentBag to ConcurrentDictionary to match the updated receptor signature. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Fix SonarCloud coverage merge by building before merge Problem: ReportGenerator was trying to merge coverage reports that referenced source-generated files (.whizbang-generated/**/*.g.cs) before those files existed, causing 'File does not exist (any more)' errors. Root Cause: Coverage artifacts from test workflows reference source-generated files from their builds. When SonarCloud workflow tried to merge these coverage reports, the files were missing because the project hadn't been built yet in this workflow. Solution: Build project BEFORE merging coverage reports to ensure all source-generated files exist. Then build again inside SonarScanner block for code analysis. Workflow order (fixed): 1. Download coverage artifacts from all test workflows 2. Build project (generates all .whizbang-generated files) 3. Merge coverage with ReportGenerator (files now exist) 4. SonarScanner begin 5. Build again (SonarScanner analyzes code during build) 6. SonarScanner end (uploads analysis + merged coverage) This adds one extra build but eliminates the coverage merge failures. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Fix SonarCloud security hotspot: use full commit SHA for nuget/login action SonarCloud flagged githubactions:S7637 - using tag instead of full commit SHA reduces supply chain security. Changed: nuget/login@v1 → NuGet/login@d22cc5f This ensures precise, verifiable dependency tracking and prevents accidental or malicious reference to unintended commits. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(security): remove overly permissive workflow permissions Remove `permissions: read-all` from security-scorecard.yml and use job-level least-privilege permissions instead. This resolves the SonarCloud vulnerability (githubactions:S8234) that was blocking the quality gate. The analysis job already had specific permissions defined, so the workflow-level read-all was both unnecessary and overly permissive. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Four regression guards covering the class of bug fixed by the FlushAsync
split:
1. FlushApiSourceInvariantTests (unit) — reads Whizbang.Core source text:
- Dispatcher.cs contains zero strategy.FlushAndGetBatchAsync() calls
(all five cascade/publish/send sites must be fire-and-forget)
- ServiceBusConsumerWorker + TransportConsumerWorker each have at
least one FlushAndGetBatchAsync (the inbox dedup sites that consume
the returned WorkBatch)
- Every IWorkFlusher.FlushAsync impl delegates to FlushAndGetBatchAsync
(end-of-request middleware cannot defer)
- Zero FlushMode references anywhere in src/ (enum is gone)
2. CascadeToOutboxIntegrationTests.IntervalStrategy_CascadedEvents_BatchUntilForceFlush
(Postgres integration) — dispatches 20 cascading commands with an
Interval strategy singleton, asserts wh_outbox is empty before the
force flush, 20 rows present after. Passes against real Postgres in
~10s.
Covers plan tasks #7 (Dispatcher call-site pinning), #8 (worker
call-site pinning), #9 (Interval integration), and #10 (FlushMode-removal
guard) with two files instead of several dozen behavior tests — the
source-text check is more durable against future refactors that update
mocks in sync with call sites.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Updated HotChocolate.Data from 15.1.11 to 15.1.12.
Release notes
Sourced from HotChocolate.Data's releases.
15.1.12
What's Changed
New Contributors
Full Changelog: ChilliCream/graphql-platform@15.1.11...15.1.12
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)