Update CF Local to v0.19.0

[sclevine]

No description provided.

[cfdreddbot]

Hey sclevine!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/156112416

The labels on this github issue will be updated when the story is started.

[sclevine]

This is blocking a release announcement for an already released version. Also, if users see the github release for v0.19.0 and runcf install-plugin cflocal, they will get an older version of the plugin and may be confused about missing features.

In the future, would it be okay for me to open this PR before making a release of CF Local, and then publish the release once the PR is merged?

Alternatively, I have write access to this repo. Are there still manual steps in the process that would prevent me from setting up a pipeline to update the plugin automatically?
(context: /pull/118)

[XenoPhex]

We'd prefer you make the PR after the plugin is released as the internal tests for the deploy try and download the assets to confirm that the SHA1s are correct.

Feel free to automate your release as long as it's submitting a PR and not commiting directly to master. Since it's still the CLI Team's responsibility to maintain this project and it's PRs, we'd prefer anyone who is not an explicit team member to submit changes via PR.

[sclevine]

We'd prefer you make the PR after the plugin is released as the internal tests for the deploy try and download the assets to confirm that the SHA1s are correct.

Got it, I'll make sure assets are available before opening the PR, and just hold off on publishing the release notes.

Feel free to automate your release as long as it's submitting a PR and not commiting directly to master. Since it's still the CLI Team's responsibility to maintain this project and it's PRs, we'd prefer anyone who is not an explicit team member to submit changes via PR.

Got it, apologies, I got a different impression from Dies. Future versions of CF Local will likely be self-updating, and that should reduce the friction. Most of the code has already moved into Docker containers anyways.