conventional-changelog/standard-version

Version at package.json not being bumped on CI environment

Open

#256 opened on Jul 17, 2018

View on GitHub
 (7 comments) (4 reactions) (0 assignees)JavaScript (7,442 stars) (825 forks)batch import
help wanted

Description

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

Contributor guide

Tech stack
javascriptnodejs
Domain
releaseci cd
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic CI/CD knowledgeNode.js environmentUnderstanding of git and versioning
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Investigate why standard version fails to bump package.json on CI. Compare local and CI environment variables (e.g., GIT COMMITTER NAME, GIT AUTHOR NAME). Check if git user is configured in CI. Look at the release tag creation logic to understand why it tags correctly but doesn't modify package.json. Review the issue comments for any similar experiences or solutions.