Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/3.5 theta #12018

Merged
merged 41 commits into from
Jul 7, 2022
Merged

Feat/3.5 theta #12018

merged 41 commits into from
Jul 7, 2022

Conversation

ZakaryCode
Copy link
Contributor

@ZakaryCode ZakaryCode commented Jun 30, 2022

这个 PR 做了什么? (简要描述所做更改)

  • 使用 pnpm workspace 替换 yarn workspace + lerna
  • 修复幽灵依赖等相关问题
  • 更新 ci 方案
    • 发布版本需要 commit message chore(release): publish [version]
    • 通过提交发布版本限制在 feat/** 分支,同时需标签信息 chore(release): publish [version] --tag=[tag]

这个 PR 是什么类型? (至少选择一个)

  • 其他,请描述(Other, please describe)

@ZakaryCode ZakaryCode force-pushed the feat/3.5-theta branch 3 times, most recently from 61483e5 to aecfe91 Compare June 30, 2022 09:29
"react-native-maps": "^0.25.0",
"react-native-pager-view": "~5.4.9",
"react-native-svg": "~12.1.1",
"react-native-webview": "~11.14.3"
},
"devDependencies": {
"@tarojs/components": "3.5.0-beta.3",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

此处删除的原因是?

Copy link
Contributor Author

@ZakaryCode ZakaryCode Jul 1, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

工作空间内的开发依赖都会改到根目录,一方面避免部分包管理工具冗余安装,另一方面也避免拓扑依赖导致的各类编译顺序问题

@ZakaryCode ZakaryCode force-pushed the feat/3.5-theta branch 6 times, most recently from 385f744 to 097f0fa Compare June 30, 2022 13:14
@ZakaryCode ZakaryCode merged commit 7229db9 into feat/3.5 Jul 7, 2022
@ZakaryCode ZakaryCode deleted the feat/3.5-theta branch July 7, 2022 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants