conventional-changelog/standard-version

Version at package.json not being bumped on CI environment

Open

#256 建立於 2018年7月17日

在 GitHub 查看
 (7 留言) (4 反應) (0 負責人)JavaScript (7,442 star) (825 fork)batch import
help wanted

描述

Hello,

Obviously I'm misunderstanding something about this library. I expect it to:

  1. bump version in package.json
  2. outputting changes to CHANGELOG
  3. committing package.json and CHANGELOG.md
  4. tag a release

Every time I try it on local it does exactly that, but when I do it on my CI environment the output is almost the same, except a little detail, it does not bump the package.json. The weird thing is that it creates the release tag that corresponds to the package.json version that it didn't made.

Instead it does:

  1. outputting changes to CHANGELOG.md
  2. committing CHANGELOG.md
  3. tagging release v1.3.0

If it properly detects that the version should be 1.3.0, why it is not bumping the package.json ? Taking a look at the generated changelog it only generates the changelog for the previous version, 1.2.0, so there is some weird alignment here...

Thanks in advance

貢獻者指南