Is it possible to specify the commit range and output the Change Log?

[suzuki-shunsuke]

I imagine the following usage.

$ standard-version --dry-run --from 1.0.0 --to 2.0.0
<a name="2.0.0"></a>
# [2.0.0](https://github.com/conventional-changelog/standard-version/compare/v1.1.0...v2.0.0) (2016-04-09)


* feat(conventional-changelog-standard): Move to conventional-changelog-standard style. This style lifts the character limit on commit messages, and puts us in a position to make more opinionated decisions in the future. ([c7ccadb](https://github.com/conventional-changelog/standard-version/commit/c7ccadb))


### BREAKING CHANGES

* we no longer accept the preset configuration option.


<a name="1.1.0"></a>
# [1.1.0](https://github.com/conventional-changelog/standard-version/compare/v1.0.0...v1.1.0) (2016-04-08)


### Features

* **cli:** use conventional default commit message with version ([9fadc5f](https://github.com/conventional-changelog/standard-version/commit/9fadc5f))
* **rebrand:** rebrand recommended-workflow to standard-version (#9) ([1f673c0](https://github.com/conventional-changelog/standard-version/commit/1f673c0))
* **tests:** adds test suite, fixed several Node 0.10 issues along the way ([03bd86c](https://github.com/conventional-changelog/standard-version/commit/03bd86c))

I want to use standard-version in the existing repository which has already several tags (1.0.0, 1.1.0, 1.1.1, 2.0.0, ...),
but standard-version seems to generate the Change Log from the last semver tags so can't generate the Change Log of the existing commits.

Even if standard-version can't do what I want to do,
if there is the another way to do it, tell me the way.

I have found some related issues but I can't solve the above problem.

• Should be able to easily generate changelog for any previous version(s). conventional-changelog#45
• feat: generate changelog from scratch #201
• How to specify a range? #93

Best regards.

[noreiller]

Hi, while trying to resolve my issue (#203), I think I have a solution for you:

You need to change the call arguments to conventionalChangelog() (https://github.com/conventional-changelog/standard-version/blob/master/lib/lifecycles/changelog.js#L32) like this:

BEFORE

var changelogStream = conventionalChangelog(
  { preset: 'angular' }, 
  context, 
  { merges: null }
)

AFTER

var changelogStream = conventionalChangelog(
  { preset: 'angular' }, 
  context, 
  Object.assign({ merges: null }, args.gitRawCommitsOpts)
)

This way, you can call standard-version this way:

standardVersion({
  gitRawCommitsOpts: { from: "v1.1.0" },
})

You should test as I'm not sure it really works.
Aurélien

[danielo515]

I am also interested on this. I just want to generate the changelog for my previous tags. They follows the same commit convention, so it should be possible.

[bcoe]

@noreiller perhaps this is something we could document in a docs/advanced.md file? I've opened an issue discussing adding more docs along these lines: #226

[noreiller]

@bcoe as this requires a change in the lib, it's more than an advanced use case.

[rjinski]

Late to the party but is there a recommended solution to generate the change log for an existing project?

[matatk]

I was having problems getting standard-version to work with existing projects; it wasn't finding the semver tags. However, this turned out to be because of my custom omission of the 'v' prefix for tags that I'd specified in .npmrc. Thanks to a comment on another issue, I learned that standard-version provides the --tag-prefix option to address that and it works very well for me, which was great news :-).