Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

This product is completely unusable in its current state #228

Closed
blairg23 opened this issue Dec 6, 2019 · 2 comments
Closed

This product is completely unusable in its current state #228

blairg23 opened this issue Dec 6, 2019 · 2 comments
Labels
duplicate

Comments

@blairg23
Copy link
Contributor

blairg23 commented Dec 6, 2019

This issue has not been addressed and causes the product to create an incorrect solution.

#219

Currently if I release a version at commit abcd1234 that contains the following commits:

abcd1234 - tagged v2
efgh1234
ijkl1234
mnop1234
qrst1234 - tagged v1

The resulting "release notes" will contain efgh1234 through qrst1234, but will be missing abcd1234. Similarly, v1 is missing qrst1234... This is an incorrect representation of what has been released, as I am also releasing abcd1234 and I am NOT releasing qrst1234 as it was released in v1!!
@blairg23 blairg23 mentioned this issue Dec 11, 2019
Closed
@alexcanessa
Copy link
Member

I'm doing some checks now to see if it's only the dataSource=commits that is broken or the whole thing and I'll reflect the status on the README file.

@alexcanessa
Copy link
Member

Commits should be now fixed. I'm releasing 0.17.1 and that should do.

Anyway, it's a duplicate of #229

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexcanessa @blairg23