loro/.changeset
Zixuan Chen 778ca5452d
feat: allow users to query the changed containers in the target id range (#549)
* feat: allow users to query the changed containers in the target id range

* chore: add changeset note

* chore: update cargo toml

* test: add related tests and add a commit before get_changed_container_in
2024-11-09 21:00:07 +08:00
..
chilled-ways-float.md perf: import batch optimize - use the largest snapshot first (#547) 2024-11-09 16:10:13 +08:00
config.json
funny-cats-divide.md Feat add API to query creators, the last editors/movers (#548) 2024-11-09 19:17:56 +08:00
hip-squids-train.md feat: allow users to query the changed containers in the target id range (#549) 2024-11-09 21:00:07 +08:00
hot-comics-type.md Feat add API to query creators, the last editors/movers (#548) 2024-11-09 19:17:56 +08:00
README.md
strong-penguins-peel.md

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