docs: clarify dependent package changesets

[dustinbyrne]

💡 Motivation and Context

The release guide says to select packages that changed, while dependent packages are intentionally not released automatically. That wording does not cover a core change that must also reach users through a new dependent-package release.

This update:

• tells authors to select every package that needs a release;
• explains that Changesets does not infer releases from .csproj project references;
• gives an explicit PostHog and PostHog.AspNetCore example;
• preserves the policy that unaffected dependent packages are not released automatically.

No changeset is included because this only changes repository release-process documentation, not a published package.

💚 How did you test it?

• bin/fmt --check
• git diff --check
• Fresh-context review against the package metadata, project references, and release workflow found no accuracy or ambiguity issues.

📝 Checklist

• I reviewed the submitted code.
• I added tests to verify the changes.
• I updated the docs if needed.
• No breaking change or entry added to the changelog.

If releasing new changes

• Ran pnpm changeset to generate a changeset file

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Pi coding agent (openai-codex/gpt-5.6-sol) inspected the release history and package configuration, drafted the clarification using controlled-language guidance, and ran a fresh-context review. The wording keeps package releases independent while making explicit when authors must select an affected dependent package.

[github-actions]

posthog-dotnet Compliance Report

Date: 2026-09-02 14:55:57 UTC
Duration: 4644ms

✅ All Tests Passed!

17/17 tests passed

---

Feature_Flags Tests

✅ 17/17 tests passed

View Details

Test	Status	Duration
Request Payload.Request With Person Properties Device Id	✅	325ms
Request Payload.Flags Request Uses V2 Query Param	✅	140ms
Request Payload.Flags Request Hits Flags Path Not Decide	✅	112ms
Request Payload.Flags Request Omits Authorization Header	✅	112ms
Request Payload.Token In Flags Body Matches Init	✅	112ms
Request Payload.Groups Round Trip	✅	118ms
Request Payload.Groups Default To Empty Object	✅	113ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False	✅	112ms
Request Payload.Disable Geoip Omitted Defaults To False	✅	114ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key	✅	115ms
Request Lifecycle.No Flags Request On Init Alone	✅	5ms
Request Lifecycle.No Flags Request On Normal Capture	✅	122ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests	✅	220ms
Request Lifecycle.Mock Response Value Is Returned To Caller	✅	118ms
Retry Behavior.Retries Flags On 502	✅	1118ms
Retry Behavior.Retries Flags On 504	✅	1116ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event	✅	217ms

[greptile-apps]

_{Reviews (1): Last reviewed commit: "docs: clarify dependent package changese..." | Re-trigger Greptile}