Grandiras/ATProto.NET

Fork 0

chore: release v0.6.0 #107

Merged

Grandiras merged 2 commits from release/v0.6.0 into main

2026-08-21 14:07:22 +00:00

Grandiras commented

2026-08-21 14:04:14 +00:00

Owner

Cuts the 0.6.0 release and condenses the changelog.

Release readiness

All green on main at 59234b7:

Check	Result
Unit tests	1708 passed, 0 failed, 5 skipped
Release build	0 warnings, 0 errors
`dotnet pack`	all 5 packages + symbols, now at 0.6.0
CI on `main` HEAD	`build-and-test` and `pds-integration` both green
Open issues / PRs	0 / 0

The 5 locally-skipped tests are the Aspire manifest ones; CI runs them in the Verify Aspire publish manifest step with ATPROTO_REQUIRE_INTEGRATION=1, so a skipped gate there fails the build rather than passing silently.

Why minor, not patch

AtProtoScopes.Repo(...) now throws ArgumentException for RepoAction.None (#94) — a real breaking change — plus substantial new API surface: permissioned data spaces (client #89, server #91, durable stores #102), Jetstream v2 (#83) and its HTTP archive (#85), and Tranquil PDS hosting (#78).

Commits

docs: condense the 0.5.0 and unreleased changelog sections — those two sections had grown into paragraph-length design essays. Condensed to changelog register: what changed, API names, migration notes, operational gotchas. 14546 → 7165 words. Verified lossless: identical set of issue references, same 148 top-level bullets, perf table intact. 0.4.0 and earlier were already in this style and are untouched.
chore: release v0.6.0 — Directory.Build.props 0.5.0 → 0.6.0, and [Unreleased] → [0.6.0] - 2026-08-21 with a fresh empty [Unreleased], matching how v0.5.0 was cut in #71.

Note for the release notes

The Spaces work is a large share of this release and targets an alpha proposal — no PDS release serves com.atproto.space.*, it exists only on bluesky-social/atproto#5187. Its 26 integration tests are gated off in CI because nothing releasable can run them. The changelog says plainly that it is alpha, unreviewed, and provides access control rather than confidentiality — worth flagging as preview in the tag message too.

Tagging v0.6.0 after merge is what triggers the release workflow.

🤖 Generated with Claude Code

Cuts the 0.6.0 release and condenses the changelog. ## Release readiness All green on `main` at `59234b7`: | Check | Result | | --- | --- | | Unit tests | 1708 passed, 0 failed, 5 skipped | | Release build | 0 warnings, 0 errors | | `dotnet pack` | all 5 packages + symbols, now at 0.6.0 | | CI on `main` HEAD | `build-and-test` and `pds-integration` both green | | Open issues / PRs | 0 / 0 | The 5 locally-skipped tests are the Aspire manifest ones; CI runs them in the `Verify Aspire publish manifest` step with `ATPROTO_REQUIRE_INTEGRATION=1`, so a skipped gate there fails the build rather than passing silently. ## Why minor, not patch `AtProtoScopes.Repo(...)` now throws `ArgumentException` for `RepoAction.None` (#94) — a real breaking change — plus substantial new API surface: permissioned data spaces (client #89, server #91, durable stores #102), Jetstream v2 (#83) and its HTTP archive (#85), and Tranquil PDS hosting (#78). ## Commits - `docs: condense the 0.5.0 and unreleased changelog sections` — those two sections had grown into paragraph-length design essays. Condensed to changelog register: what changed, API names, migration notes, operational gotchas. 14546 → 7165 words. Verified lossless: identical set of issue references, same 148 top-level bullets, perf table intact. 0.4.0 and earlier were already in this style and are untouched. - `chore: release v0.6.0` — `Directory.Build.props` 0.5.0 → 0.6.0, and `[Unreleased]` → `[0.6.0] - 2026-08-21` with a fresh empty `[Unreleased]`, matching how v0.5.0 was cut in #71. ## Note for the release notes The Spaces work is a large share of this release and targets an **alpha** proposal — no PDS release serves `com.atproto.space.*`, it exists only on [bluesky-social/atproto#5187](https://github.com/bluesky-social/atproto/pull/5187). Its 26 integration tests are gated off in CI because nothing releasable can run them. The changelog says plainly that it is alpha, unreviewed, and provides access control rather than confidentiality — worth flagging as preview in the tag message too. Tagging `v0.6.0` after merge is what triggers the release workflow. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Grandiras added 2 commits

2026-08-21 14:04:14 +00:00

docs: condense the 0.5.0 and unreleased changelog sections 756d3761dd

Entries in these two sections had grown into paragraph-length design
essays. Condensed to changelog register: what changed, the API names,
migration notes for breaking changes, and the operational gotchas a
consumer acts on. Dropped the rationale narration, internal
implementation reasoning, and test-count commentary.

0.4.0 and earlier were already in this style and are untouched.

No content lost: identical set of issue references, same 148 top-level
bullets, perf table intact. 14546 -> 7165 words across the two sections.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

chore: release v0.6.0

CI / pds-integration (pull_request) Successful in 25s

Details

CI / build-and-test (pull_request) Successful in 55s

Details

Sync Closures to GitHub / sync-closure (pull_request) Successful in 9s

Details

9d0c20c9f9

Minor bump rather than patch: AtProtoScopes.Repo(...) now throws for
RepoAction.None, alongside substantial new API surface (permissioned
data spaces client and server, Jetstream v2 and its HTTP archive,
Tranquil PDS hosting).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

claude-bot commented

2026-08-21 14:04:19 +00:00

Collaborator

🤖 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.

🤖 Reviewing this PR — follow along in [the action run](https://git.grandiras.net/Grandiras/claude-bot/actions/runs/365); the reply will link the full session transcript.  📜 [Live transcript](https://git.grandiras.net/Grandiras/claude-bot/src/branch/claude-logs/transcripts/Grandiras/ATProto.NET/pr-107/run-365.md) — updating every ~5 minutes while the task runs.

claude-reviewer approved these changes

2026-08-21 14:05:36 +00:00

claude-reviewer left a comment

✅ Verdict: approve — no blocking issues found.

This is a straightforward, low-risk release PR: condense the changelog and bump the version. I verified the specific claims made in the PR description directly against the two commits (docs: condense... and chore: release v0.6.0) rather than taking them on faith:

Version bump: Directory.Build.props goes 0.5.0 → 0.6.0 only, matching the stated rationale (a real breaking change plus substantial new API surface, so minor not patch).
Changelog restructure: [Unreleased] → [0.6.0] - 2026-08-21 with a fresh empty [Unreleased] above it, matching the pattern used for the 0.5.0 cut.
Losslessness of the condensation: I diffed the full set of Issue #NNN references before/after (identical, byte-for-byte matching hash), counted top-level - bullets (148 in both), and confirmed the 0.4.0-and-earlier sections are byte-for-byte unchanged (matching MD5). Word count dropped from 19451 to 12074 for the whole file, consistent with the claimed ~7.4k-word reduction in the two condensed sections.
Content check: the important operational caveats survived condensation — the Spaces alpha/no-security-review/access-control-not-confidentiality warning, the PDS secret-regeneration/volume-recreation warning, and all breaking-change migration notes are still present and clear.

Nothing incorrect or missing found. Good to merge.

⏱ 1m 8s · 29 turns · tokens: 79.9k in / 4.2k out (+2823.6k cache-read)
📜 Full session transcript

✅ **Verdict: approve** — no blocking issues found. This is a straightforward, low-risk release PR: condense the changelog and bump the version. I verified the specific claims made in the PR description directly against the two commits (`docs: condense...` and `chore: release v0.6.0`) rather than taking them on faith: - **Version bump**: `Directory.Build.props` goes `0.5.0` → `0.6.0` only, matching the stated rationale (a real breaking change plus substantial new API surface, so minor not patch). - **Changelog restructure**: `[Unreleased]` → `[0.6.0] - 2026-08-21` with a fresh empty `[Unreleased]` above it, matching the pattern used for the 0.5.0 cut. - **Losslessness of the condensation**: I diffed the full set of `Issue #NNN` references before/after (identical, byte-for-byte matching hash), counted top-level `- ` bullets (148 in both), and confirmed the 0.4.0-and-earlier sections are byte-for-byte unchanged (matching MD5). Word count dropped from 19451 to 12074 for the whole file, consistent with the claimed ~7.4k-word reduction in the two condensed sections. - **Content check**: the important operational caveats survived condensation — the Spaces alpha/no-security-review/access-control-not-confidentiality warning, the PDS secret-regeneration/volume-recreation warning, and all breaking-change migration notes are still present and clear. Nothing incorrect or missing found. Good to merge. --- ⏱ 1m 8s · 29 turns · tokens: 79.9k in / 4.2k out (+2823.6k cache-read) 📜 [Full session transcript](https://git.grandiras.net/Grandiras/claude-bot/src/branch/claude-logs/transcripts/Grandiras/ATProto.NET/pr-107/run-365.md)

Grandiras merged commit 7f672c0827 into main

2026-08-21 14:07:22 +00:00

Grandiras deleted branch release/v0.6.0

2026-08-21 14:07:22 +00:00

Grandiras referenced this pull request from a commit

2026-08-21 14:07:23 +00:00

chore: release v0.6.0 (#107)