chore(deps): update dependency grpc/grpc-swift to v1.13.2

[renovate]

This PR contains the following updates:

Package	Update	Change
grpc/grpc-swift	patch	1.13.1 -> 1.13.2

---

Release Notes

grpc/grpc-swift

v1.13.2: gRPC Swift 1.13.2

Compare Source

SemVer Patch

• Update swift-nio-ssl dependency (#​1541, #​1543, patch credit to @​oliverepper)
• Avoid an unnecessary copy in the client read state (#​1533)
• Avoid ack-ing pings twice (#​1534)
• Add a coalescing writer (#​1537, #​1539, #​1546)
• Remove unused code (#​1549)
• Bump version number to 1.13.2 (#​1550)

Other Changes

• Allow Swift Package Index to generate documentation (#​1535, #​1536)
• Update perf test precondition (#​1545)
• Use 5.8-nightly in CI (#​1547)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[strophy]

I think something is not working correctly in how we build and copy the plugin for this language, because the step of copying protoc-gen-swift into the upx stage runs from cache, rather than using the newly built binary. It might be worth unpicking the enormous heredoc RUN command in the swift build, since it doesn't offer any benefits in an intermediate build stage, and seems to be interfering with Docker's cache hit detection.

[rvolosatovs]

I think something is not working correctly in how we build and copy the plugin for this language, because the step of copying protoc-gen-swift into the upx stage runs from cache, rather than using the newly built binary. It might be worth unpicking the enormous heredoc RUN command in the swift build, since it doesn't offer any benefits in an intermediate build stage, and seems to be interfering with Docker's cache hit detection.

Interesting. Could it be that there was no actual change in the dependency?
Is there a way we can query the version from the binary itself to check that the correct version is actually used?

[strophy]

You're right! The built binary is bit-identical, I checked this by running md5sum and also verified that the linux binaries released at grpc/grpc-swift are also bit-identical for versions 1.13.1 and 1.13.2.