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

Ensure deploy is triggered in CI #6306

merged 1 commit into from Jun 26, 2019


2 participants
Copy link

commented Jun 26, 2019

Travis by default restricts deploys to branch master, therefore it was not picked for tag build as expected.

This patch ensures deploy runs for tag builds

As. a workaround v1.46.0 was published via temporary hack commit ->

Is this ready for review?: YES
Is it a breaking change?: NO

@medikoo medikoo added this to the 1.47.0 milestone Jun 26, 2019

@medikoo medikoo self-assigned this Jun 26, 2019

@medikoo medikoo added this to In progress in Serverless via automation Jun 26, 2019

@medikoo medikoo added pr/in-review and removed pr/in-progress labels Jun 26, 2019

@medikoo medikoo requested a review from pmuens Jun 26, 2019

Serverless automation moved this from In progress to Reviewer approved Jun 26, 2019


pmuens approved these changes Jun 26, 2019

Copy link

left a comment

Makes sense :shipit:

@pmuens pmuens added the enhancement label Jun 26, 2019

@medikoo medikoo merged commit 9b9c9e2 into master Jun 26, 2019

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
security/snyk - package.json (medikoo) No manifest changes detected

Serverless automation moved this from Reviewer approved to Done Jun 26, 2019

@medikoo medikoo deleted the force-deploy branch Jun 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.