-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Storage release 0.23.1 #3111
Storage release 0.23.1 #3111
Conversation
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
bd7a318
to
f59ee68
Compare
CLAs look good, thanks! |
f59ee68
to
3782401
Compare
I'm still sad about releasing features in a third-dot. |
So this didn't really qualify as a patch? |
It adds a method / exposes a new API feature (assigning a storage class to a blob). The issue is that cod written to use the feature will break if used with an earlier version of the same 0.23 release line. |
So you're saying it should have been 0.24? (Which is contrary to semver as well...but probably closer to correct) |
That would've been my preference. @lukesneeringer has a different take on it, though. |
Storage release 0.23.1
Storage 0.23.1