chore: release v0.5.0 #71
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Grandiras/ATProto.NET!71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/release-0.5.0"
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?
Release prep for v0.5.0. No runtime code changes — this bumps the shared version and closes the changelog section.
Changes
Directory.Build.props:Version0.4.0 → 0.5.0CHANGELOG.md: promote[Unreleased]→[0.5.0] - 2026-07-26, open a fresh empty[Unreleased]CHANGELOG.md: fix a dropped sentence break in theAdminClientempty-body entry — the release workflow publishes this section verbatim as the Forgejo release bodyWhat ships in 0.5.0
ATProtoNet.Aspire.Hosting) plusPdsAdminClient/AddAtProtoPdsAdmin()replace itATProtoNet.AspireandATProtoNet.Server.EntityFrameworkCoremerged intoATProtoNet.Server,ATProtoNet.Pdsdropped; published set goes 8 → 5csharpcodegen overhaul (#45)$typediscriminator, out-of-order metadata, unions), OAuth handle-resolution timeouts,PlcClientDID-path requestsFive breaking changes, all with migration notes in the changelog.
Verification
dotnet build -c Releasedotnet test tests/ATProtoNet.Tests/dotnet pack -c Release0.5.0dotnet list package --vulnerable --include-transitiveawkfromrelease.yml)Breaking changes→Security, stops before[0.4.0]After merge
Tagging
v0.5.0onmaintriggers.forgejo/workflows/release.yml, which packs and pushes to both the Forgejo feed and nuget.org, then creates the Forgejo release. That step is not part of this PR.Follow-up worth doing once the tag lands:
ATProtoNet.Pds,ATProtoNet.Aspire, andATProtoNet.Server.EntityFrameworkCoreare published on nuget.org at 0.4.0 and no longer exist. They should be deprecated there pointing at their replacements, otherwisedotnet add package ATProtoNet.Aspirekeeps quietly resolving.🤖 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.
Straightforward release-prep PR: version bump in
Directory.Build.props,CHANGELOG.mdpromotes[Unreleased]to[0.5.0] - 2026-07-26by inserting a header (leaving prior content correctly grouped under the new section, ending before[0.4.0]), and a genuine copy fix in theAdminClientempty-body entry (missing sentence break, tense corrected to past since it's now a shipped section, and the added "(see below)" correctly points at the Issue #69 entry later in the same section). Verified therelease.ymlawk extraction (/^## \[VERSION\]/to next/^## \[/) still works with the new header placement, and no other file references the old version string. No runtime code changes, nothing to flag.⏱ 0m 34s · 7 turns · tokens: 19.9k in / 2.3k out (+231.2k cache-read)
📜 Full session transcript