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
Copy file name to clipboardExpand all lines: README.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -217,19 +217,23 @@ If changes are made to `packages/wasm` see [here](./packages/wasm/README.md) for
217
217
## Package Versioning
218
218
219
219
Starting from version 7.x.x, this monorepo uses independent versioning for packages. This means:
220
+
220
221
- Each package maintains its own version number
221
222
- Only modified packages have their versions incremented during releases
222
223
- Internal package dependencies use semver ranges (e.g., ^1.2.3) instead of exact versions
223
224
- Package versions are no longer synchronized across all packages
224
225
225
226
This change improves developer experience by:
227
+
226
228
- Avoiding unnecessary version bumps for unchanged packages
227
229
- Making package version history more meaningful
228
230
- Allowing packages to evolve at their own pace
229
231
- Providing clearer dependency relationships between packages
230
232
231
233
### Breaking Changes
234
+
232
235
If you're upgrading from a previous version, note that this is a breaking change in how versions are managed. You may need to update your dependency management practices to:
236
+
233
237
- Use appropriate semver ranges for internal dependencies
234
238
- Track individual package versions instead of a single SDK version
235
239
- Handle potentially different versions of related packages
@@ -247,6 +251,7 @@ You must have at least nodejs v18 to do this.
247
251
4. Update the docs with `yarn gen:docs --push`
248
252
249
253
5. Publish packages with `yarn publish:packages`. This will:
254
+
250
255
- Prompt for version increments for modified packages
0 commit comments