Skip to content

Commit

Permalink
chore: regenerate README (#510)
Browse files Browse the repository at this point in the history
This PR was generated using Autosynth. 🌈


<details><summary>Log from Synthtool</summary>

```
2021-06-15 23:11:37,759 synthtool [DEBUG] > Executing /root/.cache/synthtool/java-spanner-jdbc/.github/readme/synth.py.
On branch autosynth-readme
nothing to commit, working tree clean
2021-06-15 23:11:38,999 synthtool [DEBUG] > Wrote metadata to .github/readme/synth.metadata/synth.metadata.

```
</details>

Full log will be available here:
https://source.cloud.google.com/results/invocations/61cfb5e0-68cd-47b3-89b4-af4a25c2c4b6/targets

- [ ] To automatically regenerate this PR, check this box. (May take up to 24 hours.)
  • Loading branch information
yoshi-automation committed Jun 15, 2021
1 parent ce3d0cd commit a9aa894
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion .github/readme/synth.metadata/synth.metadata
Expand Up @@ -4,7 +4,7 @@
"git": {
"name": ".",
"remote": "https://github.com/googleapis/java-spanner-jdbc.git",
"sha": "41a9cd49fed468f410ad226555f7b9ba46d857b3"
"sha": "ce3d0cdb5aa63753a26f55c524a6faa482884052"
}
},
{
Expand Down
6 changes: 3 additions & 3 deletions README.md
Expand Up @@ -17,18 +17,18 @@ If you are using Maven, add this to your pom.xml file:
<dependency>
<groupId>com.google.cloud</groupId>
<artifactId>google-cloud-spanner-jdbc</artifactId>
<version>2.2.2</version>
<version>2.2.3</version>
</dependency>
```

If you are using Gradle without BOM, add this to your dependencies
```Groovy
compile 'com.google.cloud:google-cloud-spanner-jdbc:2.2.2'
compile 'com.google.cloud:google-cloud-spanner-jdbc:2.2.3'
```

If you are using SBT, add this to your dependencies
```Scala
libraryDependencies += "com.google.cloud" % "google-cloud-spanner-jdbc" % "2.2.2"
libraryDependencies += "com.google.cloud" % "google-cloud-spanner-jdbc" % "2.2.3"
```

## Authentication
Expand Down

0 comments on commit a9aa894

Please sign in to comment.