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.

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

--release doesn't do what I expect #18

Closed
techtangents opened this issue Mar 3, 2021 · 5 comments
Closed

--release doesn't do what I expect #18

techtangents opened this issue Mar 3, 2021 · 5 comments

Comments

@techtangents
Copy link

I'd like to run a command which releases the Unreleased section.

e.g. before:

## [Unreleased]
### Added
- feature1
- feature2

after:

## [Unreleased]

## [1.2.3] - 2021-03-01
### Added
- feature1
- feature2

yarn changelog --release doesn't seem to do this. My changelog gets normalized, but nothing else seems to happen.

@oscarotero
Copy link
Owner

It's because you don't have the number of the unreleased version. ATM, this library doesn't generate the new version number because it can be a patch, minor or major version. This command was created to generate automatically the release date in this case:

## [1.2.3] - Unreleased
### Added
- feature1
- feature2

Maybe, a way to generate the version number is implementing something like --release=minor, --release=major, etc.

@techtangents
Copy link
Author

For my use case, it'd be convenient to pass in the version number. e.g.

--release 1.2.3

or

--release --version 1.2.3

@oscarotero
Copy link
Owner

Ok, that's easier. I'll do that.

@oscarotero
Copy link
Owner

Done!
v0.10.4 released. Now you can run --release 1.2.3

@techtangents
Copy link
Author

Wow, that was fast. Thank you very much!

Are you able to please add a new # Unreleased header above that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants