Prerelease, release and changelog
See original GitHub issueHi, I publish prereleases versions of my package and everything works fine, but once the release is ready, I would like to combine all the commits from the prereleases in the release changelog. Is there a way to do this ?
I tried the { skip: { changelog: true} }
config for prereleases, but it doesn’t help since the commits are releated to tags.
Thank you, Aurélien
Issue Analytics
- State:
- Created 6 years ago
- Reactions:26
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Pre-Release Notes for Release 20.07.28 - IBM
Present feature enhancements and usability and performance improvements that are introduced in this release. Document changes in system requirements, if ...
Read more >2.0 Pre-release Changelog - Montreal Forced Aligner
Getting closer to stable release! Fixed some bugs in how transcription and alignment accuracy were calculated. Added additional information to evaluation output ...
Read more >Nightly Build Notes for Alpha Anywhere - AWS
IMPORTANT: The nightly builds (previously called the 'pre-release' builds) are only ... These features/fixes will be included in the next official Update.
Read more >How to automate your releases, versioning & release notes ...
PATCH version when you make backwards-compatible bug fixes. Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.
Read more >Common Changelog
After a round of prereleases that each had a changelog entry, the entry for the release could simply state Stable release based on...
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 FreeTop 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
Top GitHub Comments
I was able to go around this by skipping the tag and changelog on prerelease, so on the next release it will generate the changelog based on the last actual release.
yarn release --prerelease beta --skip.changelog=true --skip.tag=true
Ideally, change logs should be generated in related to its tag (ie changes among pre release tags & changes among release tags).