.gitea/workflows/demo.yaml

@@ -7,8 +7,7 @@ on:
   push:
     branches: [ "main","releases/**" ]
     tags:
-      #- '*' # 任意的tag都会触发 
+      - '*' # 任意的tag都会触发 
-      - 'v*.*.*'
   # paths:
   #   - 'sub-project/**'
   #  - '!sub-project/docs/**' # !在正匹配之后匹配负模式（以 为前缀）将排除该路径。
@@ -85,7 +84,7 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: '22'
-          #check-latest: true
+          check-latest: true
           # cache: 'npm'
           # cache-dependency-path: '**/package-lock.json'
       - name: 安装node依赖
@@ -198,15 +197,15 @@ jobs:
     needs: check
     if: ${{ success() }}
     outputs:
-      tag-name: ${{ steps.set-tag.outputs.tag }} #设置一个输出标签,对外包露tag-name,值来自于当前job下steps下id叫set-tag的环境变量tag
+      tag-name: ${{ steps.set-tag.outputs.tag }} # 设置一个输出标签。对外包露tag-name，值来自于当前job下steps下id叫set-tag的环境变量tag
     strategy:
       matrix:
         runs-on: [ubuntu-latest] # [ubuntu-latest, macos-latest, windows-latest]
     runs-on: ${{ matrix.runs-on }}
     steps:
     - id: set-tag
-      # run: echo "tag=release-$(TZ=+8 date '+%Y-%m-%d_%H_%M_%S')" >> $GITHUB_OUTPUT #把变量输出到github的输出环境,上面的outputs就能获取到
+      # run: echo "tag=release-$(TZ=+8 date '+%Y-%m-%d_%H_%M_%S')" >> $GITHUB_OUTPUT # 把变量输出到github的输出环境，上面的outputs就能获取到
-      run: echo "tag=v$(TZ='Asia/Shanghai' date '+%Y.%m.%d%H%M%S')" >> $GITHUB_OUTPUT
+      run: echo "tag=release-$(TZ='Asia/Shanghai' date '+%Y-%m-%d_%H_%M_%S')" >> $GITHUB_OUTPUT
     - name: Create a File
       run: |
         echo "$(TZ='Asia/Shanghai' date '+%Y%m%d%H%M%S') hello from ${{ matrix.runs-on }}" > file-${{ matrix.runs-on }}.txt
@@ -244,11 +243,11 @@ jobs:
         run: |
           git config user.name "github-actions[bot]"
           git config user.email "actions@github.com"
-          #git tag -a ${{ steps.vars.outputs.tag }} -m "Automated release"
+          git tag -a ${{ steps.vars.outputs.tag }} -m "Automated release"
           # git push origin ${{ steps.vars.outputs.tag }}
           # 前往你的 GitHub: https://github.com/settings/tokens;生成一个classic token-建议 或 fine-grained token;选择至少:repo 权限
           # git push https://x-access-token:${PAT_PUSH}@github.com/${REPO}.git "$TAG"
-          #git push https://${GITEA_USER}:${GITEA_PAT}@${GITEA_HOST}/${GITEA_REPO}.git "$TAG"
+          git push https://${GITEA_USER}:${GITEA_PAT}@${GITEA_HOST}/${GITEA_REPO}.git "$TAG"
       - name: 获取跨job上游job的输出变量值
         run: echo "The tag from previous job is ${{ needs.upload.outputs.tag-name }}"
       - name: Download All Artifacts
@@ -331,70 +330,13 @@ jobs:
       - name: Extract tag name
         id: vars
         run: |
-          # TAG_NAME="${GITHUB_REF##*/}"
+          TAG_NAME="${GITHUB_REF##*/}"
-          TAG_NAME="${{ needs.upload.outputs.tag-name }}"
           echo "TAG_NAME=$TAG_NAME" >> $GITHUB_ENV
           echo "tag_name=$TAG_NAME" >> $GITHUB_OUTPUT
           echo "标签名称:$TAG_NAME"
-      #- name: "✏️ Generate release changelog"
-      #  uses: janheinrichmerker/action-github-changelog-generator@v2.3
-      #  with:
-      #    # token: ${{ secrets.GITHUB_TOKEN }} 
-      #    token: 'ec5e01f597b42492c1c7a73f9997435fc83c1093'
-      #    output: CHANGELOG.md
-      #- name: Extract current version changelog
-      #  id: extract
-      #  run: |
-      #    TAG_NAME1="${GITHUB_REF##*/}"  # v1.2.3
-      #    cat CHANGELOG.md
-      - name: Setup git tags
-        run: git fetch --tags
-      - name: 安装nodejs
-        uses: actions/setup-node@v4
-        with:
-          node-version: '22'
-      - name: Install conventional-changelog-cli
-        run: npm install -g conventional-changelog-cli
-      - name: Generate changelog from commits
-        id: changelog
-        run: |
-          #PREV_TAG=$(git tag --sort=-creatordate | grep '^v' | sed -n 2p)
-          #CURR_TAG=$(git tag --sort=-creatordate | grep '^v' | sed -n 1p)
-          #echo "## [$CURR_TAG] vs [$PREV_TAG] ($(date +%Y-%m-%d))" > CHANGELOG.md
-          #conventional-changelog -p angular -r 1 >> CHANGELOG.md
-          #cat CHANGELOG.md
-
-          CHANGELOG=$(conventional-changelog -p angular -r 2)
-          echo "CHANGELOG<<EOF" >> "$GITHUB_OUTPUT"
-          echo "$CHANGELOG 测试" >> "$GITHUB_OUTPUT"
-          echo "EOF" >> "$GITHUB_OUTPUT"
-      - name: Generate or update CHANGELOG.md
-        run: |
-          if [ ! -f CHANGELOG.md ]; then
-            echo "# Changelog" > CHANGELOG.md
-          fi
-          #只生成最近一次提交HEAD对应的变更
-          #conventional-changelog -p angular -r 0 -n node_modules/conventional-changelog-angular -i CHANGELOG.md -s
-          conventional-changelog -p angular -r 0 -i CHANGELOG.md -s
-          # https://juejin.cn/post/7053730154710827045
-          conventional-changelog -p angular -i CHANGELOG.md -s -r 0
-          # 提取本次 push 的 commit 列表
-          #git log "${{ github.event.before }}..${{ github.sha }}" --pretty=format:"%s|%h"
-          git log "${{ github.event.before }}..${{ github.sha }}" --pretty=format:"==SPLIT==%n%s%n%b%n==END=="
-      - name: Commit & Push changelog (if changed)
-        run: |
-          git add CHANGELOG.md
-          cat CHANGELOG.md
-          if git diff --cached --quiet; then
-            echo "No changelog changes to commit."
-          else
-            git commit -m "docs(changelog): update changelog after commit"
-            git push
-          fi
-
       - name: Create Gitea Release
         id: create_release
-        run: | #API接口:https://git.ewancle.com/api/swagger和https://docs.gitea.com/zh-cn/development/api-usage,EOF必须顶格写
+        run: | #API接口:https://git.ewancle.com/api/swagger和https://docs.gitea.com/zh-cn/development/api-usage
           response=$(curl -s -X POST "${GITEA_API_URL}/repos/${GITEA_USER1}/${GITEA_REPO1}/releases" \
           -H "Authorization: token a94110b4fa993133ceb0e04fdabfd70626e02405" \
           -H "Content-Type: application/json" \
@@ -402,7 +344,7 @@ jobs:
           {
               "tag_name": "${{ env.TAG_NAME }}",
               "name": "Release ${{ env.TAG_NAME }}",
-              "body": "${{ steps.changelog.outputs.CHANGELOG }}",
+              "body": "This release was created automatically by GitHub Actions.",
               "draft": false,
               "prerelease": false
           }
@@ -419,18 +361,6 @@ jobs:
 
           echo "RELEASE_ID=$RELEASE_ID" >> $GITHUB_ENV
           echo "release_id=$RELEASE_ID" >> $GITHUB_OUTPUT
-      - name: Upload artifact to Gitea Release
-        run: |
-          FILE_NAME=$(basename $ARTIFACT_FILE)
-          echo $FILE_NAME
-          curl -X POST "${GITEA_API_URL}/repos/${GITEA_USER1}/${GITEA_REPO1}/releases/${{ env.RELEASE_ID }}/assets" \
-            -H "Authorization: token a94110b4fa993133ceb0e04fdabfd70626e02405" \
-            -H "accept: application/json" \
-            -H "Content-Type: multipart/form-data" \
-            -F "attachment=@$ARTIFACT_FILE"
-
-      - name: ✅ Done
-        run: echo "🎉 Gitea release $TAG_NAME created and file uploaded!"
       #- name: setup go
       #  uses: actions/setup-go@v5
       #  with:

CHANGELOG.md

@@ -1,4 +0,0 @@
-#  (2025-07-30)
-
-
-

api使用和版本发布.md

@@ -1,395 +0,0 @@
-接口：https://git.ewancle.com/api/swagger 和使用教程：https://docs.gitea.com/zh-cn/development/api-usage
-# 全部作用列表https://docs.gitea.com/zh-cn/development/oauth2-provider
-```xml
-activitypub	activitypub API routes: ActivityPub related operations.
-    read:activitypub	Grants read access for ActivityPub operations.
-    write:activitypub	Grants read/write/delete access for ActivityPub operations.
-admin	/admin/* API routes: Site-wide administrative operations (hidden for non-admin accounts).
-    read:admin	Grants read access for admin operations, such as getting cron jobs or registered user emails.
-    write:admin	Grants read/write/delete access for admin operations, such as running cron jobs or updating user accounts.
-issue	issues/*, labels/*, milestones/* API routes: Issue-related operations.
-    read:issue	Grants read access for issues operations, such as getting issue comments, issue attachments, and milestones.
-    write:issue	Grants read/write/delete access for issues operations, such as posting or editing an issue comment or attachment, and updating milestones.
-misc	Reserved for future usage.
-    read:misc	Reserved for future usage.
-    write:misc	Reserved for future usage.
-notification	notification/* API routes: user notification operations.
-    read:notification	Grants read access to user notifications, such as which notifications users are subscribed to and read new notifications.
-    write:notification	Grants read/write/delete access to user notifications, such as marking notifications as read.
-organization	orgs/* and teams/* API routes: Organization and team management operations.
-    read:organization	Grants read access to org and team status, such as listing all orgs a user has visibility to, teams, and team members.
-    write:organization	Grants read/write/delete access to org and team status, such as creating and updating teams and updating org settings.
-package	/packages/* API routes: Packages operations
-    read:package	Grants read access to package operations, such as reading and downloading available packages.
-    write:package	Grants read/write/delete access to package operations. Currently the same as read:package.
-repository	/repos/* API routes except /repos/issues/*: Repository file, pull-request, and release operations.
-    read:repository	Grants read access to repository operations, such as getting repository files, releases, collaborators.
-    write:repository	Grants read/write/delete access to repository operations, such as getting updating repository files, creating pull requests, updating collaborators.
-user	/user/* and /users/* API routes: User-related operations.
-    read:user	Grants read access to user operations, such as getting user repo subscriptions and user settings.
-    write:user	Grants read/write/delete access to user operations, such as updating user repo subscriptions, followed users, and user settings.
-```
-curl -X POST "https://git.ewancle.com/api/v1/users/xiehaijun/tokens" \
-  -H "Authorization: token f5856ff0aecd675b72c1910bd4a19679927a6ba0" \
-  -H "Content-Type: application/json" \
-  -d '{
-    "name": "full-access-token",
-    "scopes": [
-      "repo",
-      "repo:status",
-      "admin:repo_hook",
-      "admin:org",
-      "write:issue",
-      "write:repository",
-      "read:repository"
-    ]
-  }'
-  
-# 管理员账号进行作用域token创建 
-curl -X 'POST' \
-  'https://git.ewancle.com/api/v1/users/xiehaijun/tokens' \
-  -u 'xiehaijun:Xiehaijun945' \
-  -H 'accept: application/json' \
-  -H 'Content-Type: application/json' \
-  -d '{
-  "name": "full-access-token",
-  "scopes": [
-    "write:repository",
-    "read:repository",
-    "read:user",
-    "write:user",
-    "read:organization",
-    "write:organization"
-  ]
-}'
-
-# 全部的权限token :"sha1":"ec5e01f597b42492c1c7a73f9997435fc83c1093"
-curl -X 'POST' \
-  'https://git.ewancle.com/api/v1/users/xiehaijun/tokens' \
-  -u 'xiehaijun:Xiehaijun945' \
-  -H 'accept: application/json' \
-  -H 'Content-Type: application/json' \
-  -d '{
-  "name": "full-super-token",
-  "scopes": [
-    "read:activitypub",
-    "write:activitypub",
-    "read:admin",
-    "write:admin",
-    "read:issue",
-    "write:issue",
-    "read:misc",
-    "write:misc",
-    "read:admin",
-    "write:admin",
-    "read:notification",
-    "write:notification",
-    "read:package",
-    "write:package",
-    "write:repository",
-    "read:repository",
-    "read:user",
-    "write:user",
-    "read:organization",
-    "write:organization"
-  ]
-}'
-
-# 获取token，需要read:admin，write:admin
-curl -X 'GET' \
-  'https://git.ewancle.com/api/v1/users/xiehaijun/tokens' \
-  -H "Authorization: token a94110b4fa993133ceb0e04fdabfd70626e02405" \
-  -H 'accept: application/json'
-  
-  
-  
-
-EOF 前有空格或 Tab → 会导致闭合失败（命令行就和run: |下面的行平齐）
-你写的是 <<EOF，但忘了在最后一行独占写 EOF
-- name: Create Gitea Release
-  run: |
-    curl -s -X POST "${GITEA_API_URL}/repos/${GITEA_USER}/${GITEA_REPO}/releases" \
-      -H "Authorization: token ${{ secrets.GITEA_PAT }}" \
-      -H "Content-Type: application/json" \
-      -d @- <<EOF
-{
-  "tag_name": "${{ env.TAG_NAME }}",
-  "name": "Release ${{ env.TAG_NAME }}",
-  "body": "This is an automated release",
-  "draft": false,
-  "prerelease": false
-}
-EOF
-
-
-将 JSON 拆成变量拼接，避免复杂嵌套：
-- name: Create Gitea Release
-  run: |
-    JSON=$(jq -n --arg tag "$TAG_NAME" --arg name "Release $TAG_NAME" --arg body "Auto release" '{
-      tag_name: $tag,
-      name: $name,
-      body: $body,
-      draft: false,
-      prerelease: false
-    }')
-
-    echo "$JSON"
-
-    curl -s -X POST "${GITEA_API_URL}/repos/${GITEA_USER}/${GITEA_REPO}/releases" \
-      -H "Authorization: token ${{ secrets.GITEA_PAT }}" \
-      -H "Content-Type: application/json" \
-      -d "$JSON"
-
-
-
-
-
-非常棒的问题！为了确保 **Gitea Release 上传附件正确识别 MIME 类型（`Content-Type`）**，你在使用 `curl` 上传文件时，应当为不同文件类型设置**合适的 Content-Type**。
-
----
-
-## ✅ 常见类型对应的 `Content-Type` 设置
-
-| 文件类型               | 示例文件名                | 推荐 Content-Type                                                                  |
-| ------------------ | -------------------- | -------------------------------------------------------------------------------- |
-| `.txt`             | `README.txt`         | `text/plain`                                                                     |
-| `.zip`             | `release.zip`        | `application/zip`                                                                |
-| `.tar.gz` / `.tgz` | `release.tar.gz`     | `application/gzip`                                                               |
-| `.exe`             | `app.exe`            | `application/vnd.microsoft.portable-executable` 或 `application/octet-stream`（通用） |
-| `.md5` / `.sha256` | `release.zip.sha256` | `text/plain` 或 `application/octet-stream`（兼容性更好）                                 |
-
----
-
-### 💡 推荐策略
-
-> ❗ **通用、安全的 fallback 类型：** `application/octet-stream` 可用于所有二进制文件上传，兼容性最强。
-
----
-
-## 🧪 示例上传命令
-
-```bash
-# 上传 zip 文件
-curl -X POST "$GITEA_API_URL/repos/$OWNER/$REPO/releases/$RELEASE_ID/assets?name=release.zip" \
-  -H "Authorization: token $GITEA_PAT" \
-  -H "Content-Type: application/zip" \
-  --data-binary @"dist/release.zip"
-
-# 上传 sha256 文件
-curl -X POST "$GITEA_API_URL/repos/$OWNER/$REPO/releases/$RELEASE_ID/assets?name=release.zip.sha256" \
-  -H "Authorization: token $GITEA_PAT" \
-  -H "Content-Type: text/plain" \
-  --data-binary @"dist/release.zip.sha256"
-```
-
----
-
-## ✅ 生成验证文件示例（Shell）
-
-```bash
-# 生成 sha256 验证文件
-sha256sum dist/release.zip > dist/release.zip.sha256
-
-# 可选：生成 md5 验证文件
-md5sum dist/release.zip > dist/release.zip.md5
-```
-
----
-
-## 🔄 自动 Content-Type 映射 Bash 函数（可嵌入 GitHub Actions）
-
-```bash
-detect_content_type() {
-  case "$1" in
-    *.zip) echo "application/zip" ;;
-    *.tar.gz|*.tgz) echo "application/gzip" ;;
-    *.exe) echo "application/octet-stream" ;;
-    *.txt) echo "text/plain" ;;
-    *.md5|*.sha256) echo "text/plain" ;;
-    *) echo "application/octet-stream" ;;  # fallback
-  esac
-}
-```
-
-> 然后你就可以这样调用：
-
-```bash
-CONTENT_TYPE=$(detect_content_type "$FILENAME")
-```
-
----
-
-## ✅ 总结
-
-| 文件扩展名     | 推荐 Content-Type               |
-| --------- | ----------------------------- |
-| `.zip`    | `application/zip`             |
-| `.tar.gz` | `application/gzip`            |
-| `.exe`    | `application/octet-stream`    |
-| `.txt`    | `text/plain`                  |
-| `.sha256` | `text/plain` 或 `octet-stream` |
-| 其他未知类型    | `application/octet-stream`    |
-
----
-
-如你希望我将这些自动识别上传逻辑封装为 GitHub Actions 步骤或脚本，并上传多个文件到 Gitea，我可以帮你生成一套模板。是否继续？
-
-
-
-
-你的问题分成两大部分，我们逐一系统回答：
-
----
-
-# ✅ 一、`.xz`、`.pdf`、`.jpg`、`.mp4` 等常见文件的 Content-Type 设置
-
-| 文件扩展名            | 示例文件          | 推荐 `Content-Type`  |
-| ---------------- | ------------- | ------------------ |
-| `.xz`            | `data.tar.xz` | `application/x-xz` |
-| `.pdf`           | `manual.pdf`  | `application/pdf`  |
-| `.jpg` / `.jpeg` | `cover.jpg`   | `image/jpeg`       |
-| `.png`           | `image.png`   | `image/png`        |
-| `.mp4`           | `video.mp4`   | `video/mp4`        |
-| `.json`          | `data.json`   | `application/json` |
-| `.csv`           | `data.csv`    | `text/csv`         |
-| `.xml`           | `data.xml`    | `application/xml`  |
-
-✅ 如果不确定，可使用通用 `application/octet-stream`，**但推荐精确设置 MIME 类型**，便于 Release 页面或浏览器识别。
-
----
-
-# ✅ 二、GitHub 与 Gitee 发布 Release 并上传文件（API 对比）
-
----
-
-## ✅ GitHub：创建 Release 并上传 Asset 附件
-
-### 🔗 GitHub API 文档：
-
-* [Create Release](https://docs.github.com/en/rest/releases/releases#create-a-release)
-* [Upload Release Asset](https://docs.github.com/en/rest/releases/assets?apiVersion=2022-11-28#upload-a-release-asset)
-
-### 📦 步骤 1：创建 Release
-
-```bash
-response=$(curl -s -X POST "https://api.github.com/repos/OWNER/REPO/releases" \
-  -H "Authorization: token $GITHUB_PAT" \
-  -H "Content-Type: application/json" \
-  -d @- <<EOF
-{
-  "tag_name": "v1.2.3",
-  "name": "Release v1.2.3",
-  "body": "This is an automated release",
-  "draft": false,
-  "prerelease": false
-}
-EOF
-)
-
-upload_url=$(echo "$response" | jq -r '.upload_url' | sed 's/{?name,label}//')
-```
-
----
-
-### 📦 步骤 2：上传附件
-
-```bash
-curl -X POST "$upload_url?name=manual.pdf" \
-  -H "Authorization: token $GITHUB_PAT" \
-  -H "Content-Type: application/pdf" \
-  --data-binary @"./build/manual.pdf"
-```
-
----
-
-## ✅ Gitee：创建 Release 并上传文件（非标准，需曲线实现）
-
-### 🔗 官方文档（不完善）：
-
-* [Gitee Releases API](https://gitee.com/api/v5/swagger#/getV5ReposOwnerRepoReleases)
-
-Gitee 的限制：
-
-* ✅ 可以创建 Release（相当于发布 Tag）
-* ❌ 不支持上传附件到 Release（没有像 GitHub 的 assets 接口）
-* ✅ 可上传文件到 repo 或 wiki，或额外建专用仓库存文件
-
----
-
-### 🟡 Gitee 创建 Release 示例（只含 tag 和说明）：
-
-```bash
-curl -X POST "https://gitee.com/api/v5/repos/OWNER/REPO/releases" \
-  -H "Content-Type: application/json" \
-  -d @- <<EOF
-{
-  "access_token": "$GITEE_TOKEN",
-  "tag_name": "v1.2.3",
-  "name": "Release v1.2.3",
-  "body": "Changelog here"
-}
-EOF
-```
-
----
-
-### 🔴 Gitee 上传文件：无直接 API 可传文件到 Release 页面
-
-**替代方案：**
-
-1. 把文件上传到仓库某个目录：
-
-   ```bash
-   curl -X POST https://gitee.com/api/v5/repos/OWNER/REPO/contents/path/to/file \
-     -F access_token=$GITEE_TOKEN \
-     -F content=$(base64 ./manual.pdf) \
-     -F message="upload file"
-   ```
-
-   ⚠️ 支持 txt, md 等文本文件（base64 转码后大小限制），不推荐上传大型二进制文件。
-
-2. 使用专门的文件下载仓库或私有网盘存放链接，在 Release 中贴出 URL。
-
----
-
-# ✅ 三、总结对比：GitHub vs Gitee 发布 Release 附件能力
-
-| 操作               | GitHub                  | Gitee           |
-| ---------------- | ----------------------- | --------------- |
-| 创建 Release       | ✅                       | ✅               |
-| 上传附件到 Release 页面 | ✅ `assets` 接口           | ❌ 不支持直接上传       |
-| 支持多附件            | ✅                       | ❌（建议提供外链）       |
-| 自动化支持            | ✅ GitHub Actions / curl | ❌ 需要 workaround |
-
----
-
-## ✅ 补充建议：构建通用上传脚本
-
-你可以用如下结构自动上传任意构建产物：
-
-```bash
-file="release.tar.xz"
-mime_type=$(file --mime-type -b "$file")
-
-curl -X POST "$upload_url?name=$(basename $file)" \
-  -H "Authorization: token $TOKEN" \
-  -H "Content-Type: $mime_type" \
-  --data-binary @"$file"
-```
-
-> `file --mime-type` 自动识别 MIME 类型，适合你上传 `.xz`, `.pdf`, `.mp4` 等任意格式。
-
----
-
-## ✅ 可选扩展：GitHub Actions 中自动上传多个文件到 Release
-
-如果你希望我写一份完整的 `matrix` + MIME 自动识别 + GitHub/Gitee 多仓同时发布的 Actions，我可以马上生成。
-
-是否继续？你也可以告诉我具体构建产物目录和需要上传哪些类型，我直接帮你生成 YAML 或 Shell。
-
-
-
-
-
-
-

日志美化和手动发布以及git到其他仓库.md

@@ -1,4 +1,3 @@
-```
 name: Update Main Version
 run-name: Move ${{ github.event.inputs.major_version }} to ${{ github.event.inputs.target }}
 
@@ -42,25 +41,8 @@ https://github.com/marketplace/actions/generate-changelog#outputs
 
 
 这是个非常专业、实际的需求，下面我将以生产实践为你梳理一套完整的流程：**如何标准化 Commit 信息，并借助 GitHub Actions 自动生成高质量的 CHANGELOG，用于 `softprops/action-gh-release@v2` 展示变更内容**。
-```
----
-# github日志生成+发布仓库
-- name: Conventional Changelog Action
-  id: changelog
-  uses: TriPSs/conventional-changelog-action@v5
-  with:
-    github-token: ${{ secrets.github_token }}
-    output-file: "false"
 
-- name: Create Release
+---
-  uses: actions/create-release@v1
-  if: ${{ steps.changelog.outputs.skipped == 'false' }}
-  env:
-    GITHUB_TOKEN: ${{ secrets.github_token }}
-  with:
-    tag_name: ${{ steps.changelog.outputs.tag }}
-    release_name: ${{ steps.changelog.outputs.tag }}
-    body: ${{ steps.changelog.outputs.clean_changelog }}
 
 # ✅ 最佳实践目标