update actual version tag

Author: supervacuus

docs/platforms/native/advanced-usage/container-environments/index.mdx

@@ -8,9 +8,9 @@ sidebar_order: 2000
 The Sentry Native SDK uses a [database path](https://docs.sentry.io/platforms/native/configuration/options/#database-path) to store events and crash reports. When you are using a containerized environment, you may want to mount a volume to persist the database across container restarts to avoid losing this data.
 
 ## Waiting for `Crashpad` to Finish
-Starting with SDK version [0.8.3](https://github.com/getsentry/sentry-native/releases/tag/0.8.3) for Linux and [0.8.6](https://github.com/getsentry/sentry-native/releases/tag/0.8.6) for Windows, the [option `crashpad_wait_for_upload`](https://docs.sentry.io/platforms/native/configuration/options/#crashpad-wait-for-upload) allows the application to wait for the `crashpad_handler` to finish before a shutdown-after-crash.
+Starting with SDK version [0.8.3](https://github.com/getsentry/sentry-native/releases/tag/0.8.3) for Linux and [0.9.0](https://github.com/getsentry/sentry-native/releases/tag/0.9.0) for Windows, the [option `crashpad_wait_for_upload`](https://docs.sentry.io/platforms/native/configuration/options/#crashpad-wait-for-upload) allows the application to wait for the `crashpad_handler` to finish before a shutdown-after-crash.
 
-In SDK versions older than `0.8.3`/`0.8.6`, you could use a script similar to the example below to tie container shutdown to the `crashpad_handler` process:
+In SDK versions older than `0.8.3`/`0.9.0`, you could use a script similar to the example below to tie container shutdown to the `crashpad_handler` process:
 ```bash
 #!/bin/bash