Repository navigation
Point install guidance and READMEs at 1.3.0 - #1667
Merged
Merged
Conversation
Advance the published install identity to 1.3.0 and run install:sync, add the 1.3.0 highlights row to both GitHub READMEs, and state the DSH 0.2.0 minimum in the npm package README. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017nbv2on9C7pTri9KWxVk5x
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017nbv2on9C7pTri9KWxVk5x
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 58 minutes. View limit details
✨ Finishing Touches: 💡 1
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Requested by Vain · project thread
Why the change
DeepSeekBot 1.3.0 is published on npm (
latest= 1.3.0, npm release run green), so the public install identity, README highlights and npm package README should point at it.Refs #1616.
Special things to note
scripts/install-release.jsonadvances to 1.3.0 after publication, asdocs/agents/changelog.mdrequires;pnpm install:syncrewrote the install specs in both READMEs and both installation guides.@deepseek-ai/dsh@0.2.0-rc.2, the currentlatest) only shows on npmjs.com with the next publish.pnpm changelog:check✅,pnpm install:synctheninstall:checkclean,oxfmt --checkon the changed Markdown ✅.pnpm lintfails locally onscripts/ci-plan.mjsreporting unclassifiedapps/mobile/**files; that is red on main since Mobile 2 tracer: the phone app connects to a real Host and shows the live Roster #1661 and not touched here.Change outline
Before: READMEs and guides install
deepseekbot@1.2.1; the highlights table starts at 1.2.1; the npm README says "the DSH 0.2 line from0.2.0-rc.1".After: everything installs
deepseekbot@1.3.0; a 1.3.0 row leads both highlights tables; the npm README says DSH 0.2.0 or later; one Documentation change fragment.AI assistance is welcome; the submitter must understand and validate the change. Do not include secrets or private data.
🤖 Generated with Claude Code
https://claude.ai/code/session_017nbv2on9C7pTri9KWxVk5x
Generated by Claude Code