docs(android): release notes for SDK 7.1.4 and Gradle plugin 4.0.6

docs/sdk/android/gradle-plugin/releases.mdx

@@ -9,6 +9,31 @@ slug: "/sdk/android/gradle-plugin/releases"
 
 ## 4.x (SDK 7.x)
 
+### 4.0.6 (August 2026)
+
+Stops Bugsee being added to build variants that do not include the SDK, and fixes two crashes and a
+build failure. Recommended for everyone; essential if you include Bugsee in some build variants
+only.
+
+- **Build variants without Bugsee are left alone.** If you add Bugsee for some variants only — for
+  example with `debugImplementation`, so it is in your debug builds but not in release — your
+  release builds were still being wired up to call an SDK that was not there. Depending on your
+  setup that either failed the release build, or produced an app that crashed the moment it was
+  opened. Release builds are now left untouched unless Bugsee is genuinely part of them. Flavors are
+  handled the same way. If you declare Bugsee with plain `implementation`, nothing changes for you.
+
+- **Fixes a crash on launch in apps using Compose.** Requires **Bugsee Android SDK 7.1.4** or newer,
+  which ships the matching runtime change.
+
+- **Fixes a crash in apps using thread instrumentation.**
+
+- **Failed operations are now timed.** A database or file operation that ended in an exception was
+  left looking as though it had never finished. Exception handling in your own code is unchanged.
+
+- **Manifest optimization is applied only when your SDK version supports it.**
+
+- **Third-party libraries that arrive already minified are left as they are.**
+
 ### 4.0.5 (August 2026)
 
 Restores Jetpack Compose instrumentation on Kotlin 2.2, 2.3 and 2.4. Upgrade if your project uses

docs/sdk/android/release-notes.md

@@ -7,6 +7,40 @@ slug: "/sdk/android/release-notes"
 
 Release history for Bugsee Android SDK 7.x. Looking for the previous major version? See the [6.x release notes](/sdk/android/v6/release-notes). See the [migration guide](/sdk/android/migration) when planning your upgrade from 6.x.
 
+## 7.1.4
+
+A patch release that keeps Bugsee out of your test runs and fixes three crashes that could reach
+your users.
+
+- **Your local unit tests pass again.** Bugsee could cause failures in ordinary JVM unit tests — in
+  your own code, on lines that had nothing to do with Bugsee. Tests now run unaffected. If you
+  turned off `mainThreadMisuse`, `log`, `thread` or `operationDispatch` instrumentation to get a
+  green test run, you can turn them back on.
+
+- **Trouble inside Bugsee can no longer surface from your logging calls.** Logging statements in
+  your app are now unaffected by anything that happens while Bugsee is capturing.
+
+- **Fixes a crash when the report screen is reopened.** Reporting an issue could crash if Android
+  restored the screen after your app had been dropped from memory in the background.
+
+- **Fixes a crash when the theme changes while a report is open.** Switching the device between
+  light and dark mode with a notification-opened report on screen crashed the app.
+
+- **The notification icon appears again on devices that need the fallback.** On Huawei devices
+  running Android 6.0 and older, Bugsee's notification showed no small icon.
+
+- **Screenshots are no longer lost on some storage configurations.** Where the device restricted how
+  Bugsee stores identical screenshots, the screenshot was dropped from the report instead of being
+  saved another way.
+
+## 7.1.3
+
+A single fix for how notification-initiated reports are labelled.
+
+- **Reports opened from the Bugsee notification are attributed correctly.** They were recorded as if
+  they had been started from code, so they could not be told apart from reports opened with
+  `Bugsee.showReportDialog()`.
+
 ## 7.1.2
 
 A patch release for native crash reporting. Crashes in the first moments of a launch — a window that