chore: update dependencies and pin the CI PDS version #220
No reviewers
Labels
No labels
breaking-change
bug
documentation
duplicate
enhancement
good first issue
help wanted
performance
question
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Grandiras/ATProto.NET!220
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-219-deps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #219.
Packages
System.Formats.Cbor,Microsoft.Extensions.{Caching,Logging}.Abstractions, EF Core (Relational, Sqlite),AspNetCore.TestHostAspire.Hosting,.AppHost,.PostgreSQL,Aspire.AppHost.SdkMicrosoft.Extensions.Http.Resilience(sample)StackExchange.Redis(sample)Microsoft.NET.Test.Sdkcoverlet.collectorNSubstituteZstdSharp.Portxunit.v3→xunit.v3.mtp-off,xunit.runner.visualstudioMicrosoft.CodeAnalysis.CSharp(doc-snippet generator)Two deliberate choices:
xunit.v3.mtp-off. The defaultxunit.v34.x runs on Microsoft.Testing.Platform v2, which refuses the VSTest mode ofdotnet teston the .NET 10 SDK. Moving to MTP would change every documented and CI command line,--filterincluded. Themtp-offvariant is the same xunit 4 run throughxunit.runner.visualstudio.CI PDS
pds-integrationnow runsghcr.io/bluesky-social/pds:0.4.5037(the newest release, digestsha256:3a8feb34…, which equals today'slatest). A runner that doesn't force pulls could keep an oldlatestcached indefinitely. CONTRIBUTING's local integration setup uses the same pin.Build has 0 warnings; 5110 unit tests pass, including a
--filterrun.🤖 Generated with Claude Code
🤖 Reviewing this PR — the review will link the full session transcript.
📜 Live transcript — updating every ~5 minutes while the review runs.
🤖 Reviewing this PR — follow along in the action run; the reply will link the full session transcript.
📜 Live transcript — updating every ~5 minutes while the task runs.
✅ Verdict: approve — no blocking issues found.
This is a clean dependency bump, and I found nothing that should block merging. I read the diff and grepped the repo, but didn't build or run the tests; the PR reports a 0-warning build and 5110 passing unit tests.
Microsoft.ExtensionsandSystem.Formats.Cborversions all move together, as the comments in the csproj files require. The Roslyn 5.0 pin for the source generator is a sound choice, as the PR explains. No stale10.0.10or13.4.6references remain.pds:latest:docs/managed-pds.md:483andsamples/ManagedPdsSample/README.md:65still sayghcr.io/bluesky-social/pds:latest. These are user-facing examples for running a managed PDS, so leaving them unpinned is defensible. If you want one pinned version across the repo, update them too.StackExchange.Redisgoes from 2.x to 3.x, but it is only used in the doc-snippets project. The compiled doc build is the check there, and the PR says it passes.🧠 claude-sonnet-5-5 · ⏱ 0m 10s · 3 turns · tokens: 18.7k in / 783 out (+42.4k cache-read)
📜 Full session transcript
✅ Verdict: approve — no blocking issues found.
Good, careful dependency bump. Verified against reality:
0.4.5037resolves on ghcr, and at review time its digest (sha256:3a8feb34…) is identical to whatlatestpoints at, matching the PR's claim. Pinning CI and CONTRIBUTING's local setup to the same tag removes the stale-cached-latestambiguity in the service container.xunit.v3.mtp-off4.0.1 exists and is exactly the "xunit 4 without Microsoft.Testing.Platform" package (it pullsxunit.v3.core.mtp-off), sodotnet testkeeps its VSTest mode and documented--filterbehavior withxunit.runner.visualstudio4.0.0.tests/Directory.Build.propsalready carries thexUnit1051NoWarn with an honest comment, and CI'sTreatNoTestsAsError=trueguards on both filtered test runs remain in place.One non-blocking consistency point (no action required for this PR):
docs/managed-pds.md(~line 483) andsamples/ManagedPdsSample/README.md(~line 65) still showpds:latestin their run-your-own-PDS instructions. Those target end users standing up a persistent server rather than the test setup, solatestis defensible there, but if the intent is "pin everywhere the docs tell a human to launch the reference PDS," these are the two spots left behind. Similarly,AtProtoPdsHostingExtensions.DefaultTagis still"latest"for the Aspire resource default — reasonable for a library API, just noting both in case you want them tracked.⏱ 2m 1s · 28 steps · $0.0268 · tokens: 49.9k in / 3.0k out (+510.5k cache-read) · Go: 5h 3% · wk 2% · mo 92%
📜 Full session transcript