Closed gyanta closed 2 years ago
This pull request is automatically built and testable in CodeSandbox.
To see build info of the built libraries, click here or the icon next to each commit SHA.
@gyanta Sorry, please run prettier or eslint --fix
locally or on GitPod.
Oops, missed that - thanks @JounQin!
Thanks for your contribution! @gyanta
My pleasure, thanks for all your work on this!
@wooorm I believe we can publish a stable v2 version now.
ping @wooorm
I’ll try to get to it tomorrow. Please ping me if I don’t!
Are you sure everything is ready for a stable? 2.0.0
? Exciting!
I am guessing that yarn release
will make a patch? How do you want me to release it?
Are you sure everything is ready for a stable? 2.0.0? Exciting!
From my personal view, yes it's! I've been using the beta version for a long time.
I am guessing that yarn release will make a patch? How do you want me to release it?
I think yarn release
will just do the right thing.
Or you can try yarn release --dry-run
at least.
I think it’s making a next release right now 🤔
lerna publish major --conventional-commits --create-release github --yes
^-- this probably?
(Lerna seems bad for version management for this point. 😅)
I've migrated to https://github.com/changesets/changesets for most of my projects.
lerna publish major --conventional-commits --create-release github --yes
^-- this probably?
Maybe, hope it will work correctly. 😅
nope :'(
lerna notice cli v4.0.0
lerna info current version 2.0.0-next.6
lerna notice Current HEAD is already released, skipping change detection.
lerna success No changed packages to publish
Is there like a force flag?
@wooorm
https://github.com/mdx-js/eslint-mdx/pull/396#issuecomment-1126907016
You'd better to do dry-run
first?
@wooorm
Or force push back the latest commit first to generate a correct changelog?
boom, worked!
Can you manage the release notes?
Can you manage the release notes?
Yes, just going to do this and change the changelog manually.
Closes #400