Skip to content

docs: clarify dependent package changesets #313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dustinbyrne merged 1 commit into from
Sep 2, 2026
Merged

docs: clarify dependent package changesets #313

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,12 +24,14 @@ When making a releasable change, run:
pnpm changeset
```

Select the package or packages that changed:
Select every package that needs a release:

- Core SDK change: select `PostHog`
- ASP.NET Core integration change: select `PostHog.AspNetCore`
- AI Observability change: select `PostHog.AI`

Changesets does not infer dependent-package releases from the `.csproj` project references. Select a dependent package when its next release must require the new `PostHog` version. For example, select both `PostHog` and `PostHog.AspNetCore` when users must receive a core fix by updating `PostHog.AspNetCore`. Apply the same rule to `PostHog.AI`. Do not select all dependent packages for every core change. The packages release independently by design.

Then choose the bump type:

- `patch`: bug fixes, documentation updates, dependency-only updates, and internal changes
Expand Down Expand Up @@ -72,7 +74,7 @@ You can manually trigger the release workflow from the Actions tab with `workflo
- The root `package.json` is tooling-only and is not released.
- The workflow publishes packages sequentially with `PostHog` first, because the other packages depend on it.
- If only `PostHog.AI` changes, only `PostHog.AI` is versioned and published.
- If only `PostHog` changes, only `PostHog` is versioned and published, including for major releases.
- If a changeset selects only `PostHog`, only `PostHog` is versioned and published, including for major releases.
- Do not add internal `dependencies` entries to the package-specific `package.json` files unless you intentionally want Changesets to couple those packages' releases.

## Troubleshooting
Expand Down
Loading