Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump @liveblocks/client from 1.12.0 to 2.13.0 #36

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 1, 2024

Bumps @liveblocks/client from 1.12.0 to 2.13.0.

Release notes

Sourced from @​liveblocks/client's releases.

2.13.0

@liveblocks/react-ui

  • Add a formatting toolbar to Composer which appears when selecting text. It’s enabled by default in the default components and can also be custom built with new primitives (Composer.FloatingToolbar and Composer.MarkToggle) and new APIs (const { marks, toggleMark } = useComposer()).
  • Add new --lb-line-height token to control the line height of main elements (e.g. comment bodies in comments and composers).
  • Remove Timestamp export mistakenly added to @liveblocks/react-ui, it should be imported from @liveblocks/react-ui/primitives instead.

2.12.2

@liveblocks/react-tiptap

  • Add new options for useLiveblocksExtension() to allow setting initialContent, experimental offline support, and the field name
  • Update floating composer to support onComposerSubmit handler and closing the composer with the escape key

@liveblocks/zustand

  • Add support for Zustand v5

2.12.1

@liveblocks/react-ui

  • Prevent unsupported attachment previews from loading infinitely.
  • Refactored Thread and Comment component to be usable outside of the RoomProvider component.

2.12.0

This release adds support for tracking synchronization status of pending local changes for any part of Liveblocks. Whether you use Storage, Text Editors, Threads, or Notifications.

If the client’s sync status is synchronized, it means all local pending changes have been persisted by our servers. If there are pending local changes in any part of Liveblocks you’re using, then the client’s sync status will be synchronizing.

Also, we’re introducing a way to prevent browser tabs from being closed while local changes are not yet synchronized. To opt-in to this protection, enable preventUnsavedChanges option on the client:

  • In React: <LiveblocksProvider preventUnsavedChanges />
  • Otherwise: createClient({ preventUnsavedChanges: true })

@liveblocks/client

@liveblocks/react

  • Add new hook useSyncStatus that can be used to tell whether Liveblocks is synchronizing local changes to the server. Useful to display a "Saving..." spinner in your application, when used with useSyncStatus({ smooth: true }).
  • Deprecated APIs:
    • useStorageStatus is now deprecated in favor of useSyncStatus.

@liveblocks/react-ui

  • Take composers into account when the new preventUnsavedChanges option is set.

... (truncated)

Changelog

Sourced from @​liveblocks/client's changelog.

2.13.0

@liveblocks/react-ui

  • Add a formatting toolbar to Composer which appears when selecting text. It’s enabled by default in the default components and can also be custom built with new primitives (Composer.FloatingToolbar and Composer.MarkToggle) and new APIs (const { marks, toggleMark } = useComposer()).
  • Add new --lb-line-height token to control the line height of main elements (e.g. comment bodies in comments and composers).
  • Remove Timestamp export mistakenly added to @liveblocks/react-ui, it should be imported from @liveblocks/react-ui/primitives instead.

2.12.2

@liveblocks/react-tiptap

  • Add new options for useLiveblocksExtension() to allow setting initialContent, experimental offline support, and the field name
  • Update floating composer to support onComposerSubmit handler and closing the composer with the escape key

@liveblocks/zustand

  • Add support for Zustand v5

2.12.1

@liveblocks/react-ui

  • Prevent unsupported attachment previews from loading infinitely.
  • Refactored Thread and Comment component to be used outside of the RoomProvider component.

2.12.0

This release adds support for tracking synchronization status of pending local changes for any part of Liveblocks. Whether you use Storage, Text Editors, Threads, or Notifications.

If the client’s sync status is synchronized, it means all local pending changes have been persisted by our servers. If there are pending local changes in any part of Liveblocks you’re using, then the client’s sync status will be synchronizing.

Also, we’re introducing a way to prevent browser tabs from being closed while local changes are not yet synchronized. To opt-in to this protection, enable preventUnsavedChanges option on the client:

  • In React: <LiveblocksProvider preventUnsavedChanges />

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by liveblocks-bot, a new releaser for @​liveblocks/client since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 1, 2024
Bumps [@liveblocks/client](https://github.com/liveblocks/liveblocks/tree/HEAD/packages/liveblocks-client) from 1.12.0 to 2.13.0.
- [Release notes](https://github.com/liveblocks/liveblocks/releases)
- [Changelog](https://github.com/liveblocks/liveblocks/blob/main/CHANGELOG.md)
- [Commits](https://github.com/liveblocks/liveblocks/commits/v2.13.0/packages/liveblocks-client)

---
updated-dependencies:
- dependency-name: "@liveblocks/client"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@github-actions github-actions bot force-pushed the dependabot/npm_and_yarn/liveblocks/client-2.13.0 branch from d792311 to b608a53 Compare December 1, 2024 12:06
Copy link

netlify bot commented Dec 1, 2024

Deploy Preview for clone-figmaa failed. Why did it fail? →

Name Link
🔨 Latest commit b608a53
🔍 Latest deploy log https://app.netlify.com/sites/clone-figmaa/deploys/674c5155d296f000087f526a

@sanidhyy
Copy link
Owner

sanidhyy commented Dec 1, 2024

@dependabot ignore this dependency

@dependabot dependabot bot closed this Dec 1, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 1, 2024

OK, I won't notify you about @liveblocks/client again, unless you re-open this PR.

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/liveblocks/client-2.13.0 branch December 1, 2024 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant