You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: switch to independent per-package versioning (#116)
Remove linked versioning so each package (b2c-cli, b2c-tooling-sdk,
b2c-dx-mcp) versions independently based on its own changesets. The
publish pipeline now compares each package's local version against npm
and only publishes packages that have actually changed.
Copy file name to clipboardExpand all lines: AGENTS.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,11 +127,17 @@ See [testing skill](./.claude/skills/testing/SKILL.md) for patterns on writing t
127
127
128
128
## Changesets
129
129
130
-
This project uses [Changesets](https://github.com/changesets/changesets) for version management. When making changes that affect users, create a changeset:
130
+
This project uses [Changesets](https://github.com/changesets/changesets) for version management with **independent per-package versioning**. Each package versions independently based on its own changesets.
131
+
132
+
**How it works:**
133
+
- A changeset affecting only the SDK bumps only the SDK version
134
+
- Packages that depend on a bumped package get an automatic patch bump (via `updateInternalDependencies: "patch"`) — e.g., if SDK bumps, CLI and MCP auto-get a patch bump because they depend on it
135
+
- Only packages with a newer version than what's on npm get published
131
136
132
137
Changeset guidelines:
133
-
- Create a changeset for any user-facing changes (features, bug fixes); typically in new pull requests;
138
+
- Create a changeset for any user-facing changes (features, bug fixes); typically in new pull requests
134
139
- a pull request can have multiple changesets; separate files for separate changes
140
+
- Only list directly-changed packages in changeset frontmatter — do not include dependent packages (they get auto-bumped)
135
141
- Select the appropriate semver bump: `patch` (bug fixes) or `minor` (new features)
136
142
- This is a pre-1.0 preview release, so there are no `major` breaking change bumps yet
137
143
- Good changesets explain:
@@ -151,4 +157,4 @@ create a changeset file directly in `.changeset/` with a unique filename (e.g.,
151
157
Description of the change explaining WHAT, WHY, and HOW to update
152
158
```
153
159
154
-
- Include only the packages that were modified
160
+
- Include only the packages that were directly modified
0 commit comments