-
Notifications
You must be signed in to change notification settings - Fork 241
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
CHANGELOG – Week 20 #1612
Merged
Merged
CHANGELOG – Week 20 #1612
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### **[Add your changes](https://github.com/liveblocks/liveblocks/edit/CHANGELOG-WEEK-1/CHANGELOG_PUBLIC.md)** Click above to edit the file, and add your new changes. Will be published on **Friday, 10th of May.** ## Example ```md # Week 19 (2024-05-12) ## v1.1.1 ### `@liveblocks/react` - Added a new hook for fetching threads from notifications. - Fixed a problem with thread caching. ## v1.1.0 ### `@liveblocks/node` - Fix "process is undefined" issue in Vite builds. ## Dashboard - Improved onboarding flow. - New inline quickstart guide. ## Contributors pierrelevaillant, guillaumesalles, stevenfabre ``` ### Full example <details><summary>Toggle</summary> <p></p> ```md # Week 1 (2024-06-12) ## v1.1.1 ### `@liveblocks/react` - Fixed a bug ### `@liveblocks/react-comments` - Added a new component. ## v1.1.0 ### `@liveblocks/node` - Fix "process is undefined" issue in Vite builds. This issue was already fixed for `@liveblocks/core`, but not for `@liveblocks/node` yet. ## Infrastructure - REST API allows for longer room IDs, up to 128 characters. ## Documentation - New guide on [using your Y.Doc on the server](https://liveblocks.io/docs/guides/how-to-use-your-ydoc-on-the-server). ## Examples - Added mobile support for [Canvas Comments example](https://liveblocks.io/examples/canvas-comments/nextjs-comments-canvas). - Next.js Starter Kit now has a new room type. ## Dashboard - Improved onboarding flow. - New inline quickstart guide. ## Website - New blog post: [Liveblocks 1.12: Advanced filtering and custom notifications](https://liveblocks.io/blog/liveblocks-1-12-advanced-filtering-and-custom-notifications). - Added a new changelog section. ## Contributors pierrelevaillant, guillaumesalles, stevenfabre ``` </details> ## How is it published? The website deploys what it sees in `CHANGELOG_PUBLIC.md` on `main`. When this PR is merged, the next deployment will show the new entries.
pierrelevaillant
added
the
weekly changelog
After releasing a change, add it to this PR
label
May 14, 2024
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Ignored Deployments
|
Deployment failed with the following error:
|
CTNicholas
approved these changes
May 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add your changes
Click above to edit the file, and add your new changes. Will be published on Friday, 17th of May.
Example
Full example
Toggle
How is it published?
The website deploys what it sees in
CHANGELOG_PUBLIC.md
onmain
. When this PR is merged, the next deployment will show the new entries.