Chore/update docs workflow

[GeWuYou]

Summary by Sourcery

CI:

• Restrict the docs publish workflow to version tags starting with 'v' and gated main-branch commits, and migrate the build steps from Node/npm to Bun.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the docs publish GitHub Actions workflow to only trigger on version tags or explicit release commits, and switches the docs build from Node/npm to Bun.

File-Level Changes

Change	Details	Files
Restrict workflow triggers to version tags and specific main-branch release commits.	Change tag trigger pattern from all tags to only tags starting with 'v'. Add an if condition on the job to run for version tags without prerelease suffixes. Allow running on main only when the head commit message contains a specific release marker.	.github/workflows/publish-docs.yml
Migrate docs build tooling in the workflow from Node/npm to Bun.	Replace actions/setup-node with oven-sh/setup-bun using the latest Bun version. Switch dependency installation from npm install to bun install in the docs directory. Switch build command from npm run build to bun run build in the docs directory. Update inline comments to reference Bun instead of Node.	.github/workflows/publish-docs.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 2 issues, and left some high level feedback:

• The job-level if condition references github.event.head_commit.message, which may be undefined for tag pushes and can cause evaluation errors; consider explicitly guarding with github.event_name == 'push' && github.ref == 'refs/heads/main' before accessing head_commit.
• Using bun-version: latest makes the workflow non-deterministic over time; consider pinning Bun to a specific major/minor version to keep docs builds reproducible.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The job-level `if` condition references `github.event.head_commit.message`, which may be undefined for tag pushes and can cause evaluation errors; consider explicitly guarding with `github.event_name == 'push' && github.ref == 'refs/heads/main'` before accessing `head_commit`.
- Using `bun-version: latest` makes the workflow non-deterministic over time; consider pinning Bun to a specific major/minor version to keep docs builds reproducible.

## Individual Comments

### Comment 1
<location> `.github/workflows/publish-docs.yml:21-22` </location>
<code_context>
 jobs:
   build-and-deploy:
+    if: |
+      (startsWith(github.ref, 'refs/tags/v') && !contains(github.ref, '-'))
+      || (github.ref == 'refs/heads/main' && contains(github.event.head_commit.message, '[release doc]'))
     runs-on: ubuntu-latest

</code_context>

<issue_to_address>
**issue (bug_risk):** The `main` branch condition in `if:` can never be true with the current trigger configuration.

Because this workflow only runs on `push` to tags (`on.push.tags: 'v*'`), the `github.ref == 'refs/heads/main'` condition will never be true here. If you want to publish docs from `main` with `[release doc]` in the commit message, add a `branches: [main]` (or similar) under `on.push`. If not, remove the `main` branch part of the `if:` to avoid dead code.
</issue_to_address>

### Comment 2
<location> `.github/workflows/publish-docs.yml:37` </location>
<code_context>
-          node-version: 20
-          cache: 'npm'
-
+          bun-version: latest
       # 3️⃣ 安装依赖
       - name: Install Dependencies
</code_context>

<issue_to_address>
**suggestion (bug_risk):** Using `bun-version: latest` reduces reproducibility and may cause unexpected breakages.

Please pin Bun to a specific version or at least a major/minor range to keep the docs build reproducible and avoid CI breakages when Bun releases new versions (e.g. `bun-version: 1.1.x` or a known-good explicit version).
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}