Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: don't update the package.json version before npm stage #25

Merged
merged 3 commits into from
Mar 25, 2019

Conversation

amcgee
Copy link
Member

@amcgee amcgee commented Mar 25, 2019

Pass NPM_CONFIG_ALLOW_SAME_VERSION to npm publish so it doesn't fail when we've already updated the package.json version in the updateDeps plugin.

@amcgee amcgee requested a review from varl March 25, 2019 10:33
Copy link
Contributor

@varl varl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's see if it flies!

@amcgee
Copy link
Member Author

amcgee commented Mar 25, 2019

🐦

@amcgee amcgee merged commit 5909f78 into master Mar 25, 2019
dhis2-bot pushed a commit that referenced this pull request Mar 25, 2019
# [0.13.0](v0.12.1...v0.13.0) (2019-03-25)

### Bug Fixes

* don't update the package.json version before npm stage ([#25](#25)) ([5909f78](5909f78))

### Features

* semantic release update deps ([#24](#24)) ([d2c155e](d2c155e))
@dhis2-bot
Copy link
Contributor

@amcgee amcgee deleted the fix/dont-update-version-before-npm branch March 25, 2019 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants