loro/.changeset
Zixuan Chen 9c1005d92e
fix: prevent merging remote changes based on local changeMergeInterval config (#614)
* docs: make the merge interval unit clear

* fix: prevent merging remote changes with small intervals and improve commit message handling

The changeMergeInterval config should only work for local changes.

* docs: refine docs
2025-01-09 12:00:52 +08:00
..
config.json Refactor: merge two js packages (#532) 2024-10-29 21:46:56 +08:00
popular-ghosts-travel.md feat: add exportJsonInIdSpan and make peer compression optional (#602) 2025-01-05 01:25:15 +08:00
README.md docs: update the release guide 2024-10-09 19:33:32 +08:00
rude-candles-jog.md fix: prevent merging remote changes based on local changeMergeInterval config (#614) 2025-01-09 12:00:52 +08:00
tame-spies-attack.md feat: find id spans between (#607) 2025-01-06 11:15:10 +08:00

Release new versions of loro-wasm and loro-crdt

  • Run pnpm changeset in the root of the repository. The generated markdown files in the .changeset directory should be committed to the repository.
  • Run git cliff -u | pbcopy to generate the changelog and copy it. Then edit the new changelog file.
  • Create PR and merge into main. The GitHub Action will create another PR that once be merged new versions of specified npm packages will be published.

Release Manually

  • Run pnpm changeset in the root of the repository. The generated markdown files in the .changeset directory should be committed to the repository.
  • Run git cliff -u | pbcopy to generate the changelog and copy it. Then edit the new changelog file.
  • Run nr release-wasm to build the WASM crate
  • Run pnpm changeset version to update the version info
  • Commit the changed files
  • Run pnpm changeset publish to publish the packages to npm
  • git push && git push --tags