Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #883 +/- ##
=========================================
Coverage 85.19% 85.19%
+ Complexity 2624 2623 -1
=========================================
Files 145 145
Lines 14287 14287
Branches 1379 1379
=========================================
Hits 12172 12172
Misses 1539 1539
Partials 576 576 Continue to review full report at Codecov.
|
39a7227 to efcacda Compare efcacda to 6302db6 Compare chingor13 approved these changes Feb 22, 2021
🤖 Release is at https://.com/googleapis/java-spanner/releases/tag/v4.0.1 🌻 |
The release build has started, the log can be viewed here. 🌻 |
The release build failed! Please investigate! |
The release build has started, the log can be viewed here. 🌻 |
🥚 You hatched a release! The release build finished successfully! 💜 |
ansh0l pushed a commit to ansh0l/java-spanner that referenced this pull request Nov 10, 2022
This is an auto-generated regeneration of the .pb.go files by cloud.google.com/go/internal/gapicgen. Once this PR is submitted, genbot will update the corresponding PR to depend on the newer version of go-genproto, and assign reviewers. Whilst this or any regen PR is open in go-genproto, genbot will not create any more regeneration PRs. If all regen PRs are closed, gapicgen will create a new set of regeneration PRs once per night. If you have been assigned to review this PR, please: - Ensure that CI is passing. If it's failing, it requires your manual attention. - Approve and submit this PR if you believe it's ready to ship. That will prompt genbot to assign reviewers to the google-cloud-go PR. Corresponding google-cloud-go PR: googleapis/google-cloud-go#6545 Changes: fix: better support for fallback mode PiperOrigin-RevId: 468790263 Source-Link: googleapis/googleapis@873ab45 feat(apigeeregistry): added support for `force` field for API and API version deletion docs: updated proto comments to align with the public documentation Clients can now set the `force` field while sending delete request to allow cascade deletion of resources in the registry. PiperOrigin-RevId: 468760464 Source-Link: googleapis/googleapis@b965a25 chore: regenerate API index Source-Link: googleapis/googleapis@ed55a83 chore(servicecontrol): remove unused proto imports PiperOrigin-RevId: 468735472 Source-Link: googleapis/googleapis@cfa1b37
rajatbhatta pushed a commit to rajatbhatta/java-spanner that referenced this pull request Nov 17, 2022
🤖 I have created a release *beep* *boop* --- ### [2.7.1](googleapis/java-spanner-jdbc@v2.7.0...v2.7.1) (2022-05-27) ### Dependencies * update dependency com.google.cloud:google-cloud-spanner-bom to v6.25.2 ([googleapis#881](googleapis/java-spanner-jdbc#881)) ([b1980b6](googleapis/java-spanner-jdbc@b1980b6)) --- This PR was generated with [Release Please](https://.com/googleapis/release-please). See [documentation](https://.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on . Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release *beep* *boop*
4.0.1 (2021-02-22)
Bug Fixes
Documentation
Dependencies
This PR was generated with Release Please. See documentation.