Prerelease for 0.1.1 #404
Merged
Prerelease for 0.1.1 #404
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @antfu. CHANGELOG sounds great. I also agree that manually writing changes is good enough for now. |
|
NPM packages published! |
|
@LingDong- Have sent you an email about the changelog things. Please check it out. Thanks! |
|
@antfu Just replied. Sorry didn't see it earlier. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR bumps the version to 0.1.1. When I get merged, I will publish it to npm.
I think I can help to manage the npm packages since I have access to it. But there are a few things I may want to discuss with you
As I can see currently, we use issues to announce the updates, such as #322 and #399. I would propose trying to add CHANGELOG.md file or using Github Release. To better track the changes.
As for the changelog content, there are people writes it manually and also some people do it fully automatically. I personally use Conventional Commits and Standard Release for most of my projects. But introducing this forces people to write commits messages in some way, which I think it's not necessary for this project in the current stage.
Depends on how you want to do this thing, I can make the pipeline if needed.