Support adding release branch changes to master's changelog
See original GitHub issueHi!
For the https://github.com/mozilla-neutrino/neutrino-dev repository, after we released v8.2.0, we switched to treating master
as the next breaking release (v9; as yet unreleased), and have since released a v8.2.1 and v8.2.2 from a separate release/v8
branch.
auto-changelog successfully updated CHANGELOG.md
in that branch (run via a package.json
version
entry), however I’ve tried to find a way to update master
’s changelog (since that’s what people will look at when visiting the repository on GitHub), and can’t find a way to do so.
It seems like as-is, when we release v9 the master
changelog and will end up skipping straight from v8.2.0 to v9.x.x.
Is this something that’s possible to achieve at the moment? If not, what changes do you think might be required to do so?
Many thanks 😃
cc @eliperelman
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:9 (5 by maintainers)
@edmorley I’ve added my attempt at an
--include-branch
option to1.6.0
. Would be great to see if it’s at all useful for your use case (or if it even works properly) as I don’t have any decent repos to test it with.Sorry for the delayed reply – I’ve finally had a chance to try this out (mozilla-neutrino/neutrino-dev#970), and it works great. Many thanks!