This is an automated email from the ASF dual-hosted git repository. chaokunyang pushed a commit to branch release_0.17.0 in repository https://gitbox.apache.org/repos/asf/fory-site.git
commit 4496fd3e3fe1d6e64760c5634a524e497de9cbb7 Author: 慕白 <[email protected]> AuthorDate: Sun Apr 19 22:55:38 2026 +0800 Require user draft for release blog skill --- .claude/skills/release-major-version/SKILL.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/.claude/skills/release-major-version/SKILL.md b/.claude/skills/release-major-version/SKILL.md index 9b0f50164..87638c616 100644 --- a/.claude/skills/release-major-version/SKILL.md +++ b/.claude/skills/release-major-version/SKILL.md @@ -80,18 +80,20 @@ This workflow covers: ## Step 1: Write the Release Blog -1. Find the previous release blog in `blog/`, typically `blog/YYYY-MM-DD-fory_<prev>_release.md`. -2. Create the new release post by adapting the previous one instead of starting from scratch. -3. Update the post carefully: +1. Ask the user to provide the English draft for the release blog if it has not already been provided. +2. Find the previous release blog in `blog/`, typically `blog/YYYY-MM-DD-fory_<prev>_release.md`. +3. Use the previous release blog as a structural/reference template, but treat the user-provided English draft as the source content for the new post. +4. Create or revise the new release post around that English draft rather than inventing the release narrative from scratch. +5. Update the post carefully: - frontmatter `slug`, `title`, `tags`, date-based filename - opening release paragraph - compare link - PR counts / contributor counts if the post includes them - highlights/features/fixes sections - benchmark images and asset paths -4. Put blog-specific assets under `static/img/blog/fory_<version>_release/` when the post needs dedicated images. -5. If you add benchmark images, ensure the referenced static paths and copied files match exactly. -6. Validate the post for obvious copy/paste errors from the previous release. +6. Put blog-specific assets under `static/img/blog/fory_<version>_release/` when the post needs dedicated images. +7. If you add benchmark images, ensure the referenced static paths and copied files match exactly. +8. Validate the post for obvious copy/paste errors from the previous release. ## Step 1A: Bump Versioned References in Current Docs --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
