Question: Faster npm package releases

[AndyMik90]

Hi maintainers! 👋
I noticed that version 1.3.1 is available in the repository's main branch (as shown in packages/code-inspector-plugin/package.json), but the latest version published to npm is still 1.3.0.
I'm wondering if there's a way to speed up the process of publishing new versions to npm/pnpm? It would be great to have the latest changes available on package managers more quickly, especially for teams that rely on the published packages.
A few questions:
Is there a specific release schedule or process that determines when versions are published to npm?
Are there any blockers or challenges that prevent immediate publishing after code changes?
Would it be possible to automate the npm publishing process as part of your CI/CD pipeline?
Thanks for maintaining this great project! The code inspector plugin has been really helpful for our development workflow.

[zh-lx]

Oh, thank you for your feedback. I forgot to execute the pnpm pub command. At present, I use pnpm workspace for one click publishing, which I find quite convenient. I will consider integrating it into CI/CD. Thank you again for your feedback!