Create Changeset
Create a .changeset/<adjective-noun-verb>.md file with this format:
---
"@ledgerhq/<name>": minor
---
Short description of the change.
Package Names
Match exactly what's in each libs/*/package.json name field. Examples:
| Library | Package name |
|---|---|
| logs | @ledgerhq/logs |
| errors | @ledgerhq/errors |
| other | Check libs/<name>/package.json |
Impact Levels
| Level | When |
|---|---|
minor |
New features, bug fixes, non-breaking changes |
major |
Breaking changes (requires discussion) |
patch |
Internal changes, dep bumps, docs |
Description
One line, concise. Examples:
Add LocalTracer.withUpdatedContext builder methodFix dispatch crash when subscriber throwsExport TraceContext type from public API
Multiple Packages
If multiple libs are modified:
---
"@ledgerhq/logs": minor
"@ledgerhq/errors": patch
---
Description covering both changes.
File Naming
Prefer letting the CLI name and write the file — on Changesets v3 this is fully non-interactive:
pnpm changeset add --minor @ledgerhq/logs -m "Add LocalTracer.withUpdatedContext"
--major, --minor and --patch each accept comma-separated package names, so a multi-package changeset is one command:
pnpm changeset add --minor @ledgerhq/logs --patch @ledgerhq/errors -m "Description covering both changes."
If writing the file by hand instead, use a random human-readable slug matching the @changesets/cli convention (e.g. happy-cats-fly.md, silver-dogs-run.md).