Repository navigation
Create GitHub releases aggregating the CHANGELOG changes #98
Description
Activity
Any updates on this? Changelog would be good to have. There are lots of new releases recently
👋🏼 Viktor,
We don't have updates yet unfortunately. Out of curiosity, how do you keep up with platform updates?@pepicrft 👋🏻
That might sound funny, but when I want to know what changed, I just open diff since the last release and try to find the PR responsible for those changes. They usually contain some context. But this is a very tedious and slow process. When working with clients I need to know when some issues were fixed or what's new. This is the only way right now for me to answer these kinds of questions
100% agree with you we need to get better at this. There are ongoing efforts to minimize the channels/surfaces you need to keep an eye on to know what's new and has changed. Using GitHub releases will be one of the first steps towards that but not the only one :)
Reacted by WiktorThis issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action.
→ If there's no activity within a week, then a bot will automatically close this.
Thanks for helping to improve Shopify's dev tooling and experience.Shoo... making bot go away
Maybe enforcing changelog edits in each PR would solve the issue :)?
Just noticed there are release notes now:
https://github.com/Shopify/cli/releasesand wanted to say "thank you". This will help a lot :)
Reacted by Gonzalo RiestraThis issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action.
→ If there's no activity within a week, then a bot will automatically close this.
Thanks for helping to improve Shopify's dev tooling and experience.
Context
Each package in this monorepo has its CHANGELOG.md file where changesets writes the changes every time we release new versions of the packages. Because we have a changelog file per package, it's cumbersome to get an overview of all the changes of a given version. It requires the user to go through all the CHANGELOGs in the repository.
What
We are not the only ones with this need so the aggregation feature is being implemented. Once it's merged, we can leverage it to create GitHub releases aggregating all the CHANGELOG updates.