ci: add pr-compressed-size

[liweijie0812]

🤔 这个 PR 的性质是？

• 日常 bug 修复
• 新特性提交
• 文档改进
• 演示代码改进
• 组件样式/交互改进
• CI/CD 改进
• 重构
• 代码风格优化
• 测试用例
• 分支合并
• 其他

🔗 相关 Issue

💡 需求背景和解决方案

📝 更新日志

• 本条 PR 不需要纳入 Changelog

tdesign-vue-next

@tdesign-vue-next/chat

@tdesign-vue-next/auto-import-resolver

☑️ 请求合并前的自查清单

⚠️ 请自检并全部勾选全部选项。⚠️

• 文档已补充或无须补充
• 代码演示已提供或无须提供
• TypeScript 定义已补充或无须补充
• Changelog 已提供或无须提供

[github-actions]

Size Change: 0 B

Total Size: 21.3 kB

ℹ️ View Unchanged

Filename	Size
./packages/auto-import-resolver/dist/index.cjs	10.7 kB
./packages/auto-import-resolver/dist/index.js	10.7 kB

_{compressed-size-action::auto-import-resolver}

[github-actions]

Size Change: 0 B

Total Size: 72.3 kB

ℹ️ View Unchanged

Filename	Size
./packages/tdesign-vue-next-chat/es/_chunks/dep-ac5d8c89.mjs	28.3 kB
./packages/tdesign-vue-next-chat/es/_chunks/dep-c21297e3.mjs	2.16 kB
./packages/tdesign-vue-next-chat/es/attachments/index.mjs	240 B
./packages/tdesign-vue-next-chat/es/chat-actionbar/chat-actionbar-props.mjs	363 B
./packages/tdesign-vue-next-chat/es/chat-actionbar/chat-actionbar.mjs	1.57 kB
./packages/tdesign-vue-next-chat/es/chat-actionbar/index.mjs	336 B
./packages/tdesign-vue-next-chat/es/chat-content/chat-content-props.mjs	358 B
./packages/tdesign-vue-next-chat/es/chat-content/chat-content.mjs	1.99 kB
./packages/tdesign-vue-next-chat/es/chat-content/index.mjs	385 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/activity/index.mjs	322 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/activity/registry.mjs	407 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/activity/render.mjs	784 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/provider/agent-state.mjs	520 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/provider/index.mjs	219 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/shared/ComponentErrorBoundary.mjs	549 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/shared/createRegistry.mjs	978 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/shared/index.mjs	259 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/shared/useRegistrationListener.mjs	624 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/toolcall/hoc.mjs	755 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/toolcall/index.mjs	441 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/toolcall/registry.mjs	410 B
./packages/tdesign-vue-next-chat/es/chat-engine/components/toolcall/render.mjs	339 B
./packages/tdesign-vue-next-chat/es/chat-engine/hooks/index.mjs	345 B
./packages/tdesign-vue-next-chat/es/chat-engine/hooks/useAgentActivity.mjs	954 B
./packages/tdesign-vue-next-chat/es/chat-engine/hooks/useAgentState.mjs	1.22 kB
./packages/tdesign-vue-next-chat/es/chat-engine/hooks/useAgentToolcall.mjs	920 B
./packages/tdesign-vue-next-chat/es/chat-engine/hooks/useChat.mjs	686 B
./packages/tdesign-vue-next-chat/es/chat-engine/index.mjs	560 B
./packages/tdesign-vue-next-chat/es/chat-input/chat-input-props.mjs	352 B
./packages/tdesign-vue-next-chat/es/chat-input/chat-input.mjs	1.53 kB
./packages/tdesign-vue-next-chat/es/chat-input/index.mjs	321 B
./packages/tdesign-vue-next-chat/es/chat-item/chat-item-props.mjs	432 B
./packages/tdesign-vue-next-chat/es/chat-item/chat-item.mjs	1.98 kB
./packages/tdesign-vue-next-chat/es/chat-item/index.mjs	432 B
./packages/tdesign-vue-next-chat/es/chat-list/chat-list.mjs	2.78 kB
./packages/tdesign-vue-next-chat/es/chat-list/index.mjs	366 B
./packages/tdesign-vue-next-chat/es/chat-list/props.mjs	454 B
./packages/tdesign-vue-next-chat/es/chat-loading/chat-loading-props.mjs	282 B
./packages/tdesign-vue-next-chat/es/chat-loading/index.mjs	244 B
./packages/tdesign-vue-next-chat/es/chat-markdown/index.mjs	261 B
./packages/tdesign-vue-next-chat/es/chat-message/chat-message-props.mjs	436 B
./packages/tdesign-vue-next-chat/es/chat-message/chat-message.mjs	1.25 kB
./packages/tdesign-vue-next-chat/es/chat-message/index.mjs	318 B
./packages/tdesign-vue-next-chat/es/chat-reasoning/chat-reasoning-props.mjs	421 B
./packages/tdesign-vue-next-chat/es/chat-reasoning/chat-reasoning.mjs	1.19 kB
./packages/tdesign-vue-next-chat/es/chat-reasoning/index.mjs	301 B
./packages/tdesign-vue-next-chat/es/chat-sender/chat-sender-props.mjs	360 B
./packages/tdesign-vue-next-chat/es/chat-sender/chat-sender.mjs	3.01 kB
./packages/tdesign-vue-next-chat/es/chat-sender/index.mjs	357 B
./packages/tdesign-vue-next-chat/es/chat-thinking/chat-thinking-props.mjs	387 B
./packages/tdesign-vue-next-chat/es/chat-thinking/chat-thinking.mjs	943 B
./packages/tdesign-vue-next-chat/es/chat-thinking/index.mjs	334 B
./packages/tdesign-vue-next-chat/es/chatbot/index.mjs	397 B
./packages/tdesign-vue-next-chat/es/config-provider.mjs	158 B
./packages/tdesign-vue-next-chat/es/index.mjs	1.51 kB
./packages/tdesign-vue-next-chat/es/style/css.mjs	42 B
./packages/tdesign-vue-next-chat/es/style/index.css	3.97 kB
./packages/tdesign-vue-next-chat/es/utils/index.mjs	493 B

_{compressed-size-action::tdesign-vue-next-chat}

[tdesign-bot]

TDesign Component Site Preview Open

Component	Preview
tdesign-vue-next
@tdesign-vue-next/chat

[pkg-pr-new]

• tdesign-vue-next-demo

  npm i https://pkg.pr.new/@tdesign-vue-next/auto-import-resolver@6499
  

  npm i https://pkg.pr.new/tdesign-vue-next@6499
  

  npm i https://pkg.pr.new/@tdesign-vue-next/chat@6499
  

commit: 94eecc1

[github-actions]

Size Change: 0 B

Total Size: 932 kB

ℹ️ View Unchanged

Filename	Size
./packages/tdesign-vue-next/dist/plugin.css	3.02 kB
./packages/tdesign-vue-next/dist/reset.css	1.91 kB
./packages/tdesign-vue-next/dist/tdesign.css	55.1 kB
./packages/tdesign-vue-next/dist/tdesign.js	515 kB
./packages/tdesign-vue-next/dist/tdesign.min.css	50.1 kB
./packages/tdesign-vue-next/dist/tdesign.min.js	307 kB

_{compressed-size-action::tdesign-vue-next}

[uyarn]

每个PR都打一次吗？之前的逻辑是发布版本才对比size diff，感觉更合理些

[liweijie0812]

每个PR都打一次吗？之前的逻辑是发布版本才对比size diff，感觉更合理些

以前的是fork 仓库改过，到release分支才对比size diff，我的觉得对比size diff 跟pr 合理，pr 产生的大量size diff 应该在pr阶段暴露出来，发版本流程应该越简单越好，只处理下版本号和日志

[uyarn]

每个PR都打一次吗？之前的逻辑是发布版本才对比size diff，感觉更合理些

以前的是fork 仓库改过，到release分支才对比size diff，我的觉得对比size diff 跟pr 合理，pr 产生的大量size diff 应该在pr阶段暴露出来，发版本流程应该越简单越好，只处理下版本号和日志

也有一定道理 这样如果有预期外的size diff问题 比较容易区分哪个PR变化引起