Repository navigation
chore: release 1.1.0 - #32
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yuezengwu
left a comment
There was a problem hiding this comment.
Reviewed exact head e1d8730 against current main1d9518f4. This is only the package version change1.0.1 to1.1.0; implementation, dependencies/lockfile and workflows are unchanged. The minor version covers the already merged behavior additions listed in the PR, and the built CLI reports1.1.0. No correctness or packaging finding.
Independent frozen install, pnpm check, pnpm typecheck, the full pnpm test suite and pnpm check:package all passed from a clean detached worktree, including the real-tarball installation/content checks in an isolated test home. Current CI is green. Production release tagging/npm publication is a separate step: this review and any gated PR merge do not create or push a release tag.
Publish the current main as 1.1.0 (minor: new behavior). Part of #29.
Since 1.0.1:
--filter=tree:0) and subtree-only sparse checkout for managed Git sources (fix: fetch only the selected subtree with a treeless partial clone #27)sync --max-age) and waiting for busy caches instead of failing (feat: share a 60-second fetch window and wait for busy caches #30)context-tree-readskill states when to sync and how to search (docs(skills): state when context-tree-read syncs and how to search #31)Only the package version changes. Validation: frozen install,
pnpm check,pnpm typecheck,pnpm test(126 tests),pnpm check:packageall pass.After merge: tag
v1.1.0on the merge commit and push the tag to publish.🤖 Generated with Claude Code