Introduce CHANGELOG.md - Githubissues

uber-go / cadence-client

Framework for authoring workflows and activities running on top of the Cadence orchestration engine.

https://cadenceworkflow.io

MIT License

345 stars 131 forks source link

Introduce CHANGELOG.md #1153

Closed vytautas-karpavicius closed 2 years ago

vytautas-karpavicius commented 2 years ago

What changed? Introducing changelog based on Keep a Changelog format.

Collected changes from previous 0.18.5 release.

Why?

How did you test it?

Potential risks

coveralls commented 2 years ago

Pull Request Test Coverage Report for Build 4060ce04-95ea-4fb0-a142-0dc422cd9371

0 of 0 changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 63.89%

Files with Coverage Reduction	New Missed Lines	%
internal/internal_task_pollers.go	2	81.64%
<!--	Total:	2		-->

Totals
Change from base Build cbdf80a0-2747-48f3-910a-7012686c3ab4:	-0.01%
Covered Lines:	12371
Relevant Lines:	19363

💛 - Coveralls

vytautas-karpavicius commented 2 years ago

bleh. Sorry about the delay - this looks good! Lets do it.

There are some kinda-easy ways to mechanically transform these kinds of changelogs to mark a version release, think we should add a makefile target for it? Assuming we can find a script that doesn't look to bad, anyway.

I'm not against it, but marking the version isn't that hard to do manually either. IMHO we can live without it for now.