Bump version on master

This commit does not represent a release and only synchronizes CHANGELOG
from the latest release.

This is a follow up to beta yanking
This commit is contained in:
Kirill Chibisov 2023-08-16 16:34:36 +04:00 committed by GitHub
parent 8b8556798e
commit 309e6aa85a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 6 deletions

View file

@ -6,7 +6,7 @@
```toml
[dependencies]
winit = "0.29.0-beta.1"
winit = "0.29.1-beta"
```
## [Documentation](https://docs.rs/winit)
@ -114,7 +114,7 @@ clash.
| winit | ndk-glue |
| :---: | :--------------------------: |
| 0.29.0-beta.1 | `android-activity = "0.5.0-beta.1"` |
| 0.29.1-beta | `android-activity = "0.5.0-beta.1"` |
| 0.28 | `android-activity = "0.4"` |
| 0.27 | `ndk-glue = "0.7"` |
| 0.26 | `ndk-glue = "0.5"` |
@ -151,7 +151,7 @@ class. Your application _must_ specify the base class it needs via a feature fla
For example, add this to Cargo.toml:
```toml
winit = { version = "0.29.0-beta.1", features = [ "android-native-activity" ] }
winit = { version = "0.29.1-beta", features = [ "android-native-activity" ] }
[target.'cfg(target_os = "android")'.dependencies]
android_logger = "0.11.0"
@ -182,7 +182,7 @@ For more details, refer to these `android-activity` [example applications](https
If your application is currently based on `NativeActivity` via the `ndk-glue` crate and building with `cargo apk` then the minimal changes would be:
1. Remove `ndk-glue` from your `Cargo.toml`
2. Enable the `"android-native-activity"` feature for Winit: `winit = { version = "0.29.0-beta.1", features = [ "android-native-activity" ] }`
2. Enable the `"android-native-activity"` feature for Winit: `winit = { version = "0.29.1-beta", features = [ "android-native-activity" ] }`
3. Add an `android_main` entrypoint (as above), instead of using the '`[ndk_glue::main]` proc macro from `ndk-macros` (optionally add a dependency on `android_logger` and initialize logging as above).
4. Pass a clone of the `AndroidApp` that your application receives to Winit when building your event loop (as shown above).