docs: update release notes and template for clarity and structure

This commit is contained in:
bowenliang123 committed 2026-09-30 00:21:58 +08:00
1 parent 3759e39275
commit 36dc96fcb5
2 files changed
+14 -4

No files matched your search

+13 -4
View File
@@ -14,10 +14,19 @@ dsh plugin --profile web update dsh-context@latest
## What's New
The single most important user-facing change, as a narrative. Drop this section when there is no headline change.
- **<Headline change N>** — <what it is, why it matters, 2–4 sentences.>
- <Key property 1>
- <Key property 2>
(The important user-facing changes)
### Features
- ** <Headline change N>**
- <Key briefing 1>
- <Key briefing 2>
### Fixes
- ...
### Changes
- ...
## Commits
+1
View File
@@ -103,6 +103,7 @@ A DeepSeek Harness plugin for context insight, actions, and management.
## Releasing
- Version X.Y.Z, 大版本.次版本.小版本。
- Review all the commits/changes since last tagged release.
- Releases are cut by tagging: `git tag vX.Y.Z && gh release create vX.Y.Z`.
- A [GitHub Actions workflow](.github/workflows/release.yml) then builds, tests, and publishes the package to npm automatically by github workflow. Agent don't have to do or check it manually.
- Write the release notes from the [release template](.github/release_template.md)