Use automation for a changelog and release management
See original GitHub issueDescribe the documentation issue
With https://github.com/changesets/changesets/tree/main/packages/changelog-github, we’ll have thanks
mentions for contributors in our changelog and releases.
What solution would you like to see?
Enable changesets
Alternative, manage thanks
mentions manually.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:28 (28 by maintainers)
Top Results From Across the Web
How to automate your releases, versioning & release notes ...
In this article we'll explore how to automate releases, changelog, release notes generation and semantic versioning via semantic-release.
Read more >How We Have Automated Release Notes Generation
There is no automation. Anyway, it has a benefit. CHANGELOG.md is stored in the repository as the rest of the code. So, it...
Read more >Adopting Changesets for release and changelog automation
So far we've been using Lerna and Lerna Changelog. The tools work great and they are very helpful to manage and release multiple...
Read more >4 Ways to Automate Your Software Release Notes - Medium
Making Release Notes Easy With Conventional Commits By leveraging keywords such as feat , fix , docs , refactor , perf , chore...
Read more >Automate Your Release Notes
The release note space is full of articles, packages, and platforms that help you keep a changelog. There are many release note generators...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems we can now evaluate the new changelog automation workflow. What do you think?
If no objections, we should update the following parts in the maintainer guide:
https://github.com/stylelint/stylelint/blob/e3421aa7d9465f2f5272191d2036b0fd44d14145/docs/maintainer-guide/pull-requests.md?plain=1#L27-L32
https://github.com/stylelint/stylelint/blob/e3421aa7d9465f2f5272191d2036b0fd44d14145/docs/maintainer-guide/releases.md?plain=1#L8-L12
@JounQin @hudochenkov Thanks for clearing the details!
It seems good to start at a minimum to evaluate the new workflow:
We can update
CHANGELOG.md
automatically via the two things above, right? Additionally, do we need to write a custom formatter to keep the existingCHANGELOG.md
format?If auto-updating
CHANGELOG.md
will be successful, I think we can move on to further automation.