Repository navigation
Archive the Release Ledger as 1.3.0 - #1616
Merged
Merged
Conversation
Fold the 29 change fragments into Unreleased, archive it as 1.3.0 with a release summary, carry the 1.2.1 maintenance section over from the release/1.2 tag, and drop the four 1.3.0 entries 1.2.1 already shipped. Changelog site tests expect the v1.2.1 and v1.3.0 pages. 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 33 minutes. View limit details
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 |
Fold the 13 fragments merged since the first pass (design-system slices 2-4, Discord QA, full access for Browser/Computer, question cards and smaller fixes) into the 1.3.0 section, and mention the design system and MCP setup in its summary. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017nbv2on9C7pTri9KWxVk5x
Fold the design-system cleanup (#1656), Local Computer on Windows and Linux (#1639), the removed ask caps (#1648) and the corrected Bot session list entry (#1659) into 1.3.0. #1659 rewrote an already-folded fragment, so the old entry is replaced by the new one. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017nbv2on9C7pTri9KWxVk5x
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
Everything merged on main since 1.2.0/1.2.1, including the whole StyleX design-system migration (#1589, slices 1–5), needs to be archived as the 1.3.0 Release Ledger before the tag can be cut.
Refs #1589. No tag, npm publish or GitHub Release is created by this PR; those wait for explicit Human approval per
docs/agents/changelog.md.Special things to note
changes/fragment after this one lands goes into the next release.v1.2.1was cut from therelease/1.2branch, so main never had its[1.2.1]section. This PR copies that section verbatim from the tag into both ledgers, and removes the four 1.3.0 entries that 1.2.1 already shipped (Sidebar: Group Channels without a custom avatar show a stack of up to four member avatars #1270 group avatar stack, Channel 消息气泡：音频 / 图片 / 文件统一为对齐的附件卡片 #1290 attachment cards, 用户消息气泡头镜像：名字靠右、时间在左 #1298 own-message header, fix: DSH compatibility metadata blocks DeepSeekBot 1.2.0 installation on rc.2; qualify 0.1.7+ and release 1.2.1 #1425>=0.1.7-0DSH minimum, which Raise DeepSeekBot's minimum DSH version to 0.2.0 #1511 supersedes anyway).1567-hide-bot-sessionsfragment; the old ledger entry is replaced by the new one (now under Added, on by default).pnpm changelog:check✅,pnpm lint✅,vitest run apps/docs/test/changelog-release-site.test.ts apps/docs/test/changelog-public-surfaces.test.ts apps/docs/test/release-draft.test.ts✅ (12 tests).node scripts/release-draft.mjs --artifact deepseekbot --version 1.3.0 --tag v1.3.0 ... --comparison-url https://github.com/BotHarness/BotHarness/compare/v1.2.1...v1.3.0produces a valid draft payload. Not run here: the full test suite (CI) and the DSH install matrix (runs innpm-release.ymlon the tag).Change outline
Before:
Unreleasedheld the entries folded before the fragment switch, fragments sat inchanges/, and main's ledger had no 1.2.1 section.After: all fragments are folded;
Unreleasedreads "No changes since 1.3.0 yet.";## [1.3.0] - 2026-10-14carries a one-sentence summary and 300+ entries;## [1.2.1] - 2026-10-12sits between 1.3.0 and 1.2.0. The changelog site tests now expectv1.2.1.mdx/v1.3.0.mdx, seven RSS items, and the home page linking/changelog/v130.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