tuhaihe opened a new pull request, #384:
URL: https://github.com/apache/cloudberry-site/pull/384
Upgrade @docusaurus/core, @docusaurus/preset-classic,
@docusaurus/module-type-aliases, @docusaurus/plugin-client-redirects,
@docusaurus/tsconfig, and @docusaurus/types to ^3.10.2.
Breaking changes addressed across 30 files:
- Replace @theme/Unlisted with @theme/ContentVisibility in swizzled
BlogPostPage, DocItem/Layout, and MDXPage components. ContentVisibility accepts
a metadata prop and handles both unlisted and draft states.
- Migrate imports from @docusaurus/theme-common/internal to plugin-specific
client entry points (20+ swizzled components):
- Docs hooks (useDoc, useDocsSidebar, DocProvider, etc.) now come from
@docusaurus/plugin-content-docs/client.
- Blog hooks (useBlogPost, BlogPostProvider, etc.) now come from
@docusaurus/plugin-content-blog/client.
- Update useGetNewBlogList hook: blog-archive JSON path changed from
blog-archive-80c.json to p/blog-archive-f05.json [blocked]; data shape wrapped
in archive key.
- Move onBrokenMarkdownLinks to markdown.hooks per Docusaurus v4 migration
path.
- Add onUntruncatedBlogPosts: 'ignore' to suppress truncation warnings for
existing blog posts.
Build verified: client and server compile successfully.
Assisted-by: Deepseek
<!--Thank you for contributing! -->
<!--In case of an existing issue or discussions, please reference it-->
closes: #ISSUE_Number
<!--Remove this section if no corresponding issue.-->
---
## Change logs
> Describe your change clearly, including what problem is being solved or
what document is being added or updated.
## Contributor's checklist
Here are some reminders before you submit your pull request:
* Make sure that your Pull Request has a clear title and commit message. You
can take the [Git commit
template](https://github.com/apache/cloudberry/blob/main/.gitmessage) as a
reference.
* Learn the [code
contribution](https://cloudberry.apache.org/contribute/code) and [doc
contribution](https://cloudberry.apache.org/contribute/doc) guides for better
collaboration.
* Make sure that your changes deployment preview is successful.
* List your communications in the [GitHub
Issues](https://github.com/apache/cloudberry-site/issues) or
[Discussions](https://github.com/apache/cloudberry/discussions) (if has or
needed).
* Feel free to ask for the [cloudberry
committers](https://github.com/orgs/apache/teams/cloudberry-committers) or
other people to help review and approve.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
