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: Fix deploy script so that it always publishes a production build. #1105

Merged
merged 3 commits into from Oct 13, 2017

Conversation

kumar303
Copy link
Contributor

@kumar303 kumar303 commented Oct 13, 2017

Fixes #1104

I think this will work but we'll have to cut a bug fix release to fully test it. If this works I'll file an issue to follow-up with some better safety checks so it doesn't happen again.

Version `2.2.0` is broken because it's a development build.
@kumar303 kumar303 requested a review from rpl October 13, 2017 21:08
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 77eb995 on kumar303:fix-release-1104 into ff0e335 on mozilla:master.

.travis.yml Outdated
@@ -22,6 +22,9 @@ script:

## lint the github PR title.
- npm run travis-pr-title-lint
## In case Travis is building a release tag, make sure we have a production build
## before publishing to npm
- NODE_ENV=production npm run build
Copy link
Member

Choose a reason for hiding this comment

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

👍

I guess that we can use something like:

before_deploy:
- NODE_ENV=production npm run build

to run it only when we are release a new version on a tag build (https://docs.travis-ci.com/user/deployment/npm/#Running-commands-before-and-after-deploy)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh nice! I didn't know about that hook.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That will keep the build running fast when we aren't doing a deploy

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 7424433 on kumar303:fix-release-1104 into ff0e335 on mozilla:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 7424433 on kumar303:fix-release-1104 into ff0e335 on mozilla:master.

@kumar303 kumar303 merged commit 2b7afb5 into mozilla:master Oct 13, 2017
@kumar303 kumar303 deleted the fix-release-1104 branch October 13, 2017 21:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Current version of web-ext (2.2.0) on npm doesn't work
3 participants