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

Release google-http-java-client v1.31.0 #754

Merged

Conversation

kolea2
Copy link
Contributor

@kolea2 kolea2 commented Jul 31, 2019

This pull request was generated using releasetool.

07-31-2019 07:21 PDT

Implementation Changes

  • Fix ApacheHttpTransport configuration (#717)

New Features

  • Add support for nanosecond precision when parsing rfc3339 strings (#752)
  • Use NIO to set file permissions (#557)
  • Expose the default HttpClientBuilder so users can customize further (#713)

Dependencies

  • Update dependency org.apache.maven.plugins:maven-site-plugin to v3.8.2 (#753)
  • Update dependency mysql:mysql-connector-java to v8.0.17 (#750)
  • Update dependency com.google.truth:truth to v1 (#742)
  • Update dependency org.apache.maven.plugins:maven-javadoc-plugin to v3.1.1 (#741)
  • Update dependency com.google.truth:truth to v0.46 (#724)
  • Update dependency org.apache.httpcomponents:httpclient to v4.5.9 (#704)
  • Group Guava, AppEngine, OpenCensus dependencies for renovate

Documentation

  • Add GitHub repo, issue tracker metadata for javadoc site (#721)
  • Clean up javadoc warnings in OpenCensusUtils (#714)

Internal / Testing Changes

  • Adds CI test for mvn dependency:analyze and fixes missing deps (#738)
  • Configure Kokoro CI for Windows (#716)
  • Add Linkage Monitor presubmit check (#719)
  • Enable autorelease (#703)
  • new ClassName().getClass() -> ClassName.class (#751)

@kolea2 kolea2 requested a review from a team as a code owner July 31, 2019 14:21
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jul 31, 2019
@kolea2 kolea2 requested review from chingor13 and removed request for a team July 31, 2019 14:24
Copy link
Contributor

@elharo elharo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The release process should not create 1.31.0-SNAPSHOT? That's fine if so. I just ask because I know some of our other release processes never commit non-SNAPSHOT versions to head so I want to make sure that isn't the case here.

@kolea2
Copy link
Contributor Author

kolea2 commented Jul 31, 2019

@elharo, this PR changes everything from -SNAPSHOT to the latest version (1.31.0), unless I'm missing something you're seeing, can you share a link?

@elharo
Copy link
Contributor

elharo commented Jul 31, 2019

Yes, and my question is whether we want to do that? Some release processes jump straight from 1.30.2-SNAPSHOT to 1.31.0-SNAPSHOT when releasing 1.30.2 and have the non-SNAPSHOT version only on branches. But it sounds like that's not how yoshi works?

@chingor13
Copy link
Collaborator

@elharo We have one commit in master that has the non snapshot which is tagged for the release (rather than a long lived branch). The next commit is a snapshot bump.

@kolea2 kolea2 merged commit 983016d into googleapis:master Jul 31, 2019
@yoshi-automation
Copy link
Contributor

@yoshi-automation
Copy link
Contributor

The release build has started, the log can be viewed here. 🌻

@yoshi-automation
Copy link
Contributor

🥚 You hatched a release! The release build finished successfully! 💜

clundin25 pushed a commit to clundin25/google-http-java-client that referenced this pull request Aug 11, 2022
…#754)

* disabling self-signed jwt for domain wide delegation

* fix: nit fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autorelease: published cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants