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

WIP:Feat 6.0.0 #156

Closed
wants to merge 17 commits into from
Closed

WIP:Feat 6.0.0 #156

wants to merge 17 commits into from

Conversation

LuckyFBB
Copy link
Collaborator

@LuckyFBB LuckyFBB commented Sep 13, 2023

LuckyFBB and others added 17 commits May 19, 2023 11:38
Releases:
  ko@6.5.3
  create-ko@1.0.1

[skip ci]
feat(ko): auto purge cache when cache pack expired by maxAge
* feat(create-ko): add editorConfig file

* docs(changeset): add editorConfig file
* chore: update webpack-dev-server to 4.14.0

* docs(changeset): update webpack-dev-server to v4.14.0

---------

Co-authored-by: jialan <jialan@dtstack.com>
* feat: support pnpm@7+

* docs(changeset): support pnpm@7.33.0

* chore: update webpack-dev-server to 4.14.0 (DTStack#147)

* chore: update webpack-dev-server to 4.14.0

* docs(changeset): update webpack-dev-server to v4.14.0

---------

Co-authored-by: jialan <jialan@dtstack.com>

* feat: support pnpm@7+

* docs(changeset): support pnpm@7.33.0

---------

Co-authored-by: JackWang032 <64318393+JackWang032@users.noreply.github.com>
Co-authored-by: jialan <jialan@dtstack.com>
* feat(ko): add jsdoc description and export .d.ts file

* docs(changeset): add jsdoc and .d.ts file

* fix(create-ko): update jsdoc for template
Releases:
  ko@6.6.0
  ko-lint-config@2.3.0
  ko-lints@5.0.0
  create-ko@1.0.2

[skip ci]
@changeset-bot
Copy link

changeset-bot bot commented Sep 13, 2023

⚠️ No Changeset found

Latest commit: 816ef85

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Collaborator

@mumiao mumiao left a comment

Choose a reason for hiding this comment

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

仔细检查下有没有破坏性变更,符合smr规范,有破坏性变更就要增加major

@LuckyFBB
Copy link
Collaborator Author

仔细检查下有没有破坏性变更,符合smr规范,有破坏性变更就要增加major

升了pnpm 版本,版本已经升级到了 6.x

@LuckyFBB LuckyFBB changed the title Feat 6.6.0 WIP:Feat 6.0.0 Sep 14, 2023
@mumiao
Copy link
Collaborator

mumiao commented Sep 14, 2023

仔细检查下有没有破坏性变更,符合smr规范,有破坏性变更就要增加major

升了pnpm 版本,版本已经升级到了 6.x

评估下pnpm upgrade 是不是破坏性的,是的话,就往上走大版本,这不能含糊,原则问题,子产品能不能立马升级是根据你的版本规范来的,无破坏性的可以直接升的

@LuckyFBB
Copy link
Collaborator Author

仔细检查下有没有破坏性变更,符合smr规范,有破坏性变更就要增加major

升了pnpm 版本,版本已经升级到了 6.x

评估下pnpm upgrade 是不是破坏性的,是的话,就往上走大版本,这不能含糊,原则问题,子产品能不能立马升级是根据你的版本规范来的,无破坏性的可以直接升的

升级 ko 的 pnpm 版本和子产品关系不大的

@mumiao
Copy link
Collaborator

mumiao commented Sep 14, 2023

仔细检查下有没有破坏性变更,符合smr规范,有破坏性变更就要增加major

升了pnpm 版本,版本已经升级到了 6.x

评估下pnpm upgrade 是不是破坏性的,是的话,就往上走大版本,这不能含糊,原则问题,子产品能不能立马升级是根据你的版本规范来的,无破坏性的可以直接升的

升级 ko 的 pnpm 版本和子产品关系不大的

我说的是发版ko,评估pnpm是不是破坏性,ko版本要不要升级大版本,进一步影响子产品,子产品升级如果ko是大版本,就不会升级;。

@mumiao
Copy link
Collaborator

mumiao commented Sep 14, 2023

再自查下

@mumiao mumiao closed this Sep 14, 2023
@LuckyFBB LuckyFBB deleted the feat_6.6.0 branch October 26, 2023 06:07
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.

None yet

3 participants