fix(@aws-amplify/geo): Bumping @aws-sdk/client-location version to fix tslib issues

[kmagilavy]

Description of changes

Bumping @aws-sdk/client-location from 3.22.0 to 3.23.0

Issue #, if available

8967

Description of how you validated changes

Tested locally in app.

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov-commenter]

Codecov Report

Merging #9234 (c16c5a1) into main (d521d17) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #9234   +/-   ##
=======================================
  Coverage   78.17%   78.17%           
=======================================
  Files         250      250           
  Lines       18188    18188           
  Branches     3902     3902           
=======================================
  Hits        14219    14219           
  Misses       3839     3839           
  Partials      130      130           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d521d17...c16c5a1. Read the comment docs.

[TreTuna]

Thank you for this PR. I had missed this, but also already had something going on a branch I'm working on to update the sdk client to the latest, so I pulled that out to a different PR #9247 in order to update and that was merged and shipped out just now in the latest versions. If you update to aws-amplify@4.3.8, which uses @aws-amplify/geo@1.1.8, you should see it. If you still see any problems, please let us know!

[kmagilavy]

Awesome - thanks so much!

…

On Thu, Nov 18, 2021 at 5:38 PM Tré Ammatuna ***@***.***> wrote: Thank you for this PR. I had missed this, but also already had something going on a branch I'm working on to update the sdk client to the latest, so I pulled that out to a different PR #9247 <#9247> in order to update and that was merged and shipped out just now in the latest versions. If you update to ***@***.***, which uses @***@***.***, you should see it. If you still see any problems, please let us know! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9234 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIFPXGLRZT3QPR2O5VGIDLUMV56XANCNFSM5IFUKYZA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[github-actions]

This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.