Come up with a way to automate releases (and detect if a release even needs to be cut)

[jmdobry]

Detecting whether a release needs to be cut might involve regenerating and checking if git diff is not empty.

[YasharF]

Do you have any update on this by any chance? It would be really helpful to unblock #806

[YasharF]

@JustinBeckwith, @lukesneeringer , @jmdobry Is this assigned to anyone or actively on the radar? I saw that it is stated as a blocker for resolving #806 but unlike that issue this one is not tagged as "Assigned" to anyone specific on Github. I am hoping that it is not a forgotten issue.

[JustinBeckwith]

Greetings! This is not forgotten :) As a matter of fact, #1905 is a nod in this direction. The truth is, as the README states:

These client libraries are officially supported by Google. However, these libraries are considered complete and are in maintenance mode. This means that we will address critical bugs and security issues but will not add any new features. For Google Cloud Platform APIs, we recommend using google-cloud-node which is under active development.

We do tend to fix bugs as they come up, but enhancement like this will generally take a back seat to the work going on in https://github.com/googleapis/google-cloud-node.

[JustinBeckwith]

What a way to end the week! The first one of these automated PRs just landed.
#2221

This is actually done!