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

Allow dependencies to upgrade with non-breaking changes #49

Merged
merged 2 commits into from
Jan 18, 2019

Conversation

adrukh
Copy link

@adrukh adrukh commented Dec 26, 2018

Following a chat on #46 (comment), applying ^ to production dependencies' versions to remove vulnerabilities introduced by dependencies.

Before: http://snyk.io/test/github/IBM-Cloud/cf-nodejs-client
After: http://snyk.io/test/github/adrukh/cf-nodejs-client

Using the `^` notation to allow the deps of this package to move forward as long as non-breaking changes are introduced to the dependencies.

This will remove 9 out 10 vulnerabilities currently introduced by this package's dependencies.
Allow a manual release with a newer version.
@adrukh
Copy link
Author

adrukh commented Dec 26, 2018

Travis tests seem to only enforce linting on PRs, I wonder how can the functional correctness be validated. Could not run npm run test:local locally, assume it depends on a CF setup I do not have?

@adrukh
Copy link
Author

adrukh commented Dec 31, 2018

👋 @srl295 how do you suggest to proceed?

@adrukh
Copy link
Author

adrukh commented Jan 7, 2019

👋 @srl295 :)

@adrukh
Copy link
Author

adrukh commented Jan 18, 2019

👋 @srl295 :))

@jsloyer jsloyer merged commit fde6ca3 into IBM-Cloud:master Jan 18, 2019
@adrukh
Copy link
Author

adrukh commented Jan 20, 2019

THANKS!

@adrukh
Copy link
Author

adrukh commented Jan 20, 2019

Can you please update once https://www.npmjs.com/package/cf-client is updated with this release? 🙏

@adrukh
Copy link
Author

adrukh commented Jan 28, 2019

👋 @jsloyer :)

@adrukh
Copy link
Author

adrukh commented Mar 12, 2019

👋 @jsloyer will keep poking here regarding publishing a new release #sorrynotsorry :)

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.

2 participants