chore: tidy root files — drop pnpm cruft, fold changelog + release docs - #11
Conversation
Root cleanup with no runtime/library behavior change:
- Remove pnpm-lock.yaml and pnpm-workspace.yaml. The project uses npm
(package-lock.json; all CI runs npm ci/npm install). pnpm-workspace.yaml
held only a junk placeholder and was never a real workspace.
- Move CHANGELOG.{zh-CN,en-US}.md into changelog/ (basenames kept). Update
the readers/writers: docs-site/scripts/build-changelog.mjs,
scripts/prepare-publish.mjs (still copies them to the npm dist root),
README links, and the RELEASE/CLAUDE/print-changelog prose. Verified the
full build still lands dist/CHANGELOG.*.md at the publish root.
- Simplify + consolidate the release flow. npm publish is now documented as
a local step (npm run release = build + npm publish ./dist, publish-from-
dist) rather than a tag-triggered CI job, since that would need an
NPM_TOKEN repo secret. Remove .github/workflows/release.yml, fold the flow
into CLAUDE.md and AGENTS.md, and delete the standalone RELEASE.md.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 44 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Free Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (13)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request moves the changelog files into a dedicated changelog/ directory and updates all references, documentation, and build/publish scripts accordingly. It also documents the local release and npm publishing workflow in AGENTS.md and CLAUDE.md, clarifying that publishing is a local step rather than a tag-triggered CI workflow. I have no feedback to provide as there are no review comments.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
1 participant
🤔 This is a ...
🔗 Related Issues
Root directory was cluttered with stray pnpm files, two loose CHANGELOG files, and a standalone RELEASE.md whose tag→CI publish path wasn't actually usable.
💡 Background and Solution
Root-level tidy-up, no library/runtime behavior change:
pnpm-lock.yaml+pnpm-workspace.yaml. The project uses npm —package-lock.jsonis the lockfile and all CI runsnpm ci/npm install.pnpm-workspace.yamlheld only a junk placeholder (allowBuilds: esbuild: set this to true or false) and was never a real workspace.changelog/.CHANGELOG.{zh-CN,en-US}.md→changelog/CHANGELOG.{zh-CN,en-US}.md(basenames kept). Updated every reader/writer:docs-site/scripts/build-changelog.mjs,scripts/prepare-publish.mjs(still copies them to the npm dist root for discoverability), README links, and doc prose. Verifiednpm run buildstill landsdist/CHANGELOG.*.mdat the publish root.npm run release=npm run build && npm publish ./dist, publish-from-dist) instead of a tag-triggered CI job — that path needed anNPM_TOKENrepo secret to inject npm auth. Removed.github/workflows/release.yml, folded the flow intoCLAUDE.mdandAGENTS.md, and deleted the standaloneRELEASE.md.📝 Change Log
🤖 Generated with Claude Code