fix: Fix the path error in the release script and change mobile/dist in the pub:theme command to theme-mobile/dist

[zzcr]

fix: 修复发布脚本中的路径错误，将pub:theme命令中的mobile/dist更改为theme-mobile/dist

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Chores
  • Streamlined publish steps in the release workflow to use simplified commands.
  • Updated project scripts to publish targeted workspace packages for components and theme.
  • Aligned publishing configuration to maintain existing access and integrity settings.
  • Bumped versions for mobile and theme packages to 1.0.0-alpha.9.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The CI workflow’s publish step now calls new pnpm scripts (pub, pub:theme) instead of direct path-based publish commands. Root package.json adds/updates these scripts to use pnpm filters. Versions for packages/mobile and packages/theme-mobile were bumped from 1.0.0-alpha.7 to 1.0.0-alpha.9.

Changes

Cohort / File(s)	Summary
CI workflow publish step .github/workflows/dispatch-publish.yml	Replaced explicit pnpm publish commands with pnpm pub --tag ... and pnpm pub:theme --tag ...; retained existing setup/auth steps.
Root publish scripts package.json	Updated pub to pnpm --filter=@opentiny/vue-mobile publish --no-git-checks --access=public; updated pub:theme to pnpm --filter="./packages/theme-mobile/dist" publish --access=public --no-git-checks.
Version bump: mobile packages/mobile/package.json	Version updated 1.0.0-alpha.7 → 1.0.0-alpha.9.
Version bump: theme-mobile packages/theme-mobile/package.json	Version updated 1.0.0-alpha.7 → 1.0.0-alpha.9.

Sequence Diagram(s)

sequenceDiagram
  participant Dev as Maintainer
  participant GH as GitHub Actions
  participant PN as pnpm scripts
  participant NPM as npm Registry

  Dev->>GH: Dispatch publish workflow (with tag)
  GH->>PN: Run "pnpm pub --tag <tag>"
  PN->>NPM: Publish @opentiny/vue-mobile
  GH->>PN: Run "pnpm pub:theme --tag <tag>"
  PN->>NPM: Publish theme-mobile/dist

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• ci (workflow): Add automated and manual publishing pipelines. #28: Introduced the dispatch-publish workflow and initial publish scripts that this PR refactors to use pnpm filters and shorthand.

Suggested reviewers

• kagol

Poem

I thump my paws—release day cheer!
New scripts hop light, the path made clear.
Tags in tow, we bound—publish, gleam!
Mobile and theme now alpha-dream.
Carrots raised to CI’s cue—
npm burrows, versions new.
Hop, ship, done—rab-bit-do! 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 3b6cfe2 and bc8f56d.

📒 Files selected for processing (4)

• .github/workflows/dispatch-publish.yml (1 hunks)
• package.json (1 hunks)
• packages/mobile/package.json (1 hunks)
• packages/theme-mobile/package.json (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch zzc/fix-ci-workflow-0815

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.