# preview Published articles for preview. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Android Studio Rabbit 1 RC 1 now available DevFeed: [Android Studio Rabbit 1 RC 1 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-09-16T14:17:15Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Beta channel](), [Release notes](), [macOS]() Tags: [android](), [android-studio](), [beta-channel](), [macos](), [preview](), [release](), [release-notes](), [update]() ### AI overview Android Studio Rabbit 1 RC 1 is available in the Beta channel. Existing Beta-channel users can update through the IDE, while others can download it. The article directs readers to preview release notes and closed issues for features, changes, and fixed bugs. ### Source excerpt Android Studio Rabbit 1 RC 1 is now available in the Beta channel. If you already have an Android Studio build on the Beta channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Rabbit 1, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Rabbit 1, see closed issues. ## Crash-Safe & Copy-On-Write GEFS As The "Good Enough File-System" For OpenBSD DevFeed: [Crash-Safe & Copy-On-Write GEFS As The "Good Enough File-System" For OpenBSD]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T13:42:00Z Content type: article Language: en Sources: [Phoronix]() Topics: [Filesystems](), [file]() Tags: [crash](), [desktop-linux](), [file](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [porting](), [preview](), [production](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview Ori Bernstein announced an early preview of GEFS, a crash-safe, snapshotting, copy-on-write file system originally developed for 9front and now being ported to OpenBSD. The OpenBSD port is not yet production-ready or submitted for inclusion in the OpenBSD tree. ### Source excerpt Ori Bernstein announced an early preview of his Good Enough File-System "GEFS" for OpenBSD. GEFS is a crash-safe, snapshotting, copy-on-write file-system that he wrote initially for 9front and now porting to OpenBSD... ## Java 27 Delivers Post-Quantum Cryptography, Future Language Innovation, Helidon 27, JavaFX 27 DevFeed: [Java 27 Delivers Post-Quantum Cryptography, Future Language Innovation, Helidon 27, JavaFX 27]() Original publisher: [Read original article]() Author: Michael Redlich Published: 2026-09-16T10:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Java](), [java-27](), [Post-quantum cryptography](), [Cryptography](), [Security](), [Programming](), [releases]() Tags: [application-security](), [architecture-design](), [cryptography](), [development](), [digital-signature](), [helidon](), [java](), [java-27](), [java27-released](), [javafx](), [jdk-27](), [jdk-28](), [lattice](), [module](), [news](), [oracle](), [portfolio](), [post-quantum-cryptography](), [preview](), [project-valhalla](), [quantum-computing](), [release](), [security](), [structured-concurrency](), [vector]() ### AI overview Oracle released Java 27, the second non-LTS release since JDK 25. Its final feature set contains nine JEPs, including post-quantum hybrid key exchange for TLS 1.3, structured concurrency, compact object headers, JFR data redaction, the Vector API, and PEM encodings for cryptographic objects. Five features remain in preview or incubator stages. ### Source excerpt Oracle has released version 27 of the Java programming language and virtual machine. As the second non-LTS release since JDK 25, the final feature set includes nine JEPs, five of which are still progressing through the preview and incubator stages. This release focuses on strengthening security, future language innovation, and projects under the auspices of the Java Verified Portfolio. By Michael Redlich ## Amazon Linux 2027 Enters Public Preview with SELinux Enforcing by Default DevFeed: [Amazon Linux 2027 Enters Public Preview with SELinux Enforcing by Default]() Original publisher: [Read original article]() Author: Steef-Jan Wiggers Published: 2026-09-15T03:40:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Linux](), [SELinux](), [migration](), [Amazon Web Services](), [Kernel](), [amazon]() Tags: [amazon](), [amazon-linux-2027-preview](), [architecture](), [architecture-design](), [aws](), [cloud](), [development](), [devops](), [ec2](), [infrastructure](), [kernel](), [linux](), [migration](), [news](), [operating-systems](), [preview](), [selinux](), [x86-64]() ### AI overview AWS has released Amazon Linux 2027 in public preview with SELinux enforcing by default. The change may require application and migration work because policies that only logged violations on AL2023 can block applications on AL2027. The release has no announced AL2023 end-of-support date, general-availability date, or in-place migration path. ### Source excerpt AWS has released Amazon Linux 2027 in public preview, built on the AL2023 baseline with kernel 7.1 and SELinux in enforcing mode by default. Applications that pass on AL2023's permissive mode may fail under enforcing. The announcement gives no AL2023 end-of-support date, no GA date, and no in-place migration path. By Steef-Jan Wiggers ## Announcing Appwrite Firewall: traffic control for your project DevFeed: [Announcing Appwrite Firewall: traffic control for your project]() Original publisher: [Read original article]() Author: Arnab Chatterjee Published: 2026-09-04T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Firewall](), [API](), [Cloud](), [Back end]() Tags: [api](), [backend](), [cloud](), [firewall](), [preview](), [products](), [project]() ### AI overview Appwrite announces Firewall, a project-level traffic control feature built into Appwrite Cloud. It lets developers define rules for APIs, Functions, and Sites using request conditions such as IP address, path, headers, query parameters, user agent, and location. Rules can allow, deny, challenge, rate-limit, or redirect traffic, with priority ordering and an impact preview before deployment. ### Source excerpt Appwrite Firewall adds project-level traffic rules to Appwrite Cloud. Deny, bypass, challenge, rate limit, or redirect requests to your API, Functions, and Sites, with an impact preview before every change. ## Android Studio Rabbit 1 Canary 4 now available DevFeed: [Android Studio Rabbit 1 Canary 4 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-09-03T15:49:24Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Android Gradle Plugin](), [Release notes]() Tags: [android](), [android-gradle-plugin](), [android-studio](), [preview](), [release-notes]() ### AI overview Android Studio Rabbit 1 Canary 4 is available in the Canary channel. The release includes general fixes for Android Studio and Android Gradle Plugin 9.5.0-alpha04, including fixes involving the Layout Inspector, Live Edit, and Running Devices. ### Source excerpt Android Studio Rabbit 1 Canary 4 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Rabbit 1, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Rabbit 1, see closed issues. General fixes and features Below is a list of general fixes in Android Studio Rabbit 1 Canary 4 and Android Gradle Plugin 9.5.0-alpha04. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues Android Gradle Plugin Issue #549199023 BouncyCastle dependency should use BOM Layout Inspector Issue #550505817 Layout Inspector agent deadlocks the inspected app (ANR) on a foldable: FoldSupport blocks the main thread while holding the ViewLayoutInspector state lock Live Edit Issue #552582834 testVibeEditSuccessGates fails with --jvmopt=-Dstudio.threading.assertions.enabled=true Running Devices Issue #552841757 Android Studio low-quality/pixelated native device mirroring that looks like low bitrate ## Android Studio Rabbit 1 Canary 3 now available DevFeed: [Android Studio Rabbit 1 Canary 3 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-08-27T13:26:09Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Release notes](), [Android Gradle Plugin](), [bug](), [Compose](), [screenshot-testing]() Tags: [android](), [android-gradle-plugin](), [android-studio](), [bug](), [compose](), [preview](), [release-notes](), [screenshot-testing](), [testing]() ### AI overview Android Studio Rabbit 1 Canary 3 is available in the Canary channel. The release includes general fixes for Android Studio Rabbit 1 and Android Gradle Plugin 9.5.0-alpha03, along with fixes for reported issues across several development tools and features. ### Source excerpt Android Studio Rabbit 1 Canary 3 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Rabbit 1, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Rabbit 1, see closed issues. General fixes and features Below is a list of general fixes in Android Studio Rabbit 1 Canary 3 and Android Gradle Plugin 9.5.0-alpha03. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues Android Gradle Plugin Issue #550220873 AGP 9.2.0 regression: `LibraryExtension.getSourceSets()` is typed on an interface the source-set implementation no longer implements, causing ClassCastException Issue #548314106 CommonExtension.resourcePrefix has incomplete docs Compose Preview Screenshot Testing Issue #539672113 Compose Preview Screenshot Testing: false "Cyclic style parent definitions" error for a dotted-name style with explicit parent="" CPU Issue #549911097 Trace File was not parsed Device Manager Issue #541776384 Device Manager: "Add a new device..." link throws IllegalArgumentException and does nothing when the tool window toolbar is hidden Gemini Issue #549864592 Invalid StreamExperience Request. Violations: contents[18].parts[0].text: Text part must not be empty. Profilers Issue #545999552 Mouse cursor not showing full symbol name when you hover over them in Profiler's Stack Sample ## Private Preview: DigitalOcean Managed Agents Runtime Services DevFeed: [Private Preview: DigitalOcean Managed Agents Runtime Services]() Original publisher: [Read original article]() Author: Salman Paracha Published: 2026-08-25T19:01:05Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Agent Harness](), [Artificial Intelligence](), [Cloud](), [Claude Code](), [codex](), [Langgraph](), [Command-line interface]() Tags: [agents](), [ai-agents](), [apis](), [claude-code](), [cli](), [cloud](), [codex](), [coding-agents](), [digitalocean](), [gateway](), [harness](), [langgraph](), [preview](), [product-updates](), [services](), [workflows]() ### AI overview DigitalOcean announces Managed Agents Runtime Services (M.A.R.S.) in private preview, combining Harness Runtime and Action Gateway. The managed service provides cloud infrastructure for persistent, scalable agent sessions and governed access to tools, APIs, and SaaS systems. ### Source excerpt AI agents are helping developers, teams, and businesses do more: writing and executing code, conducting research, and running dynamic workflows across systems. But that ability is often bounded by where they run. Close the laptop, and the work stops there. You can't pick it up on another device, hand off to a teammate, or scale it across users. Moving agents to cloud VMs solves part of this problem; developers and companies building agent harness frameworks still have to build a high-fidelity experience that can match a local session, including agent friendly execution environments, session persistence, secure tool access, human-in-the-loop approvals, and observability. Now available in Private Preview, DigitalOcean Managed Agents Runtime Services (M.A.R.S.) provides that infrastructure as a fully managed service. It gives developers, teams, and ISVs a powerful yet lightweight environment for operating coding agents and long-running, multi-tool agentic workflows without building and managing the underlying infrastructure themselves. M.A.R.S. brings together two products: Harness Runtime provides the managed execution environment in which agents run, persist, and scale. Action Gateway gives those same agents governed access to the tools, APIs, and SaaS systems they need to complete real-world work. Rather than requiring you to rebuild your agent around a proprietary framework, M.A.R.S. lets you define an environment template that packages your preferred harness, dependencies, tools, and configuration. Designed to work with Claude Code, Codex CLI, and OpenCode, as well as agents built with LangGraph or CrewAI, giving teams the freedom to choose the agent experience that best fits their needs without being locked into a single harness or framework. Agent sessions that outlive your laptop Harness Runtime helps agent sessions run independently of any local machine. They can start in under a second and resume from a pause in as little as 200 milliseconds while preserving ## Android Studio Rabbit 1 Canary 2 now available DevFeed: [Android Studio Rabbit 1 Canary 2 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-08-20T13:34:55Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Android Gradle Plugin](), [bug](), [Compose](), [Kotlin](), [JSON]() Tags: [android](), [android-gradle-plugin](), [android-studio](), [bug](), [compose](), [json](), [kotlin](), [preview](), [release-notes]() ### AI overview Android Studio Rabbit 1 Canary 2 is available in the Canary channel. The release includes general fixes in Android Studio and Android Gradle Plugin 9.5.0-alpha02, including fixes related to Baseline Profiles, Lint JSON generation, Compose Preview, and connected devices. ### Source excerpt Android Studio Rabbit 1 Canary 2 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Rabbit 1, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Rabbit 1, see closed issues. General fixes and features Below is a list of general fixes in Android Studio Rabbit 1 Canary 2 and Android Gradle Plugin 9.5.0-alpha02. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues Baseline Profiles & ProfileInstaller Issue #543799367 Baseline profile is pulled off the device but never registered in test-result.pb, so collectBaselineProfile finds nothing and copyBaselineProfileIntoSrc deletes the committed profile Lint Issue #546124524 AGP's SarifReporter generates invalid JSON when LintFix has an ending alternative that produces no edits Preview Issue #545671285 [Compose Preview] Code/Split/Design tabs missing in Kotlin files with @Preview annotation in Android Studio Quail 3 Patch 1 Running Devices Issue #546841017 Bug: IDE has various issues with connected device, including installation and mirroring, despite all signs showing otherwise ## Jetpack XR SDK core libraries reach beta: The next milestone for Android XR DevFeed: [Jetpack XR SDK core libraries reach beta: The next milestone for Android XR]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-18T17:00:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [Jetpack XR SDK](), [Android XR](), [Jetpack](), [Compose](), [releases]() Tags: [android-xr](), [beta-announcement](), [compose](), [jetpack](), [jetpack-xr-sdk](), [preview](), [releases](), [sdk]() ### AI overview Google announces that Jetpack SceneCore, ARCore for Jetpack XR, and XR Runtime have reached beta as part of the Jetpack XR SDK. The release stabilizes APIs for Android XR development, while Jetpack Compose for XR is expected to reach beta soon. ### Source excerpt Posted by Amy Zeppenfeld, Developer Relations Engineer, Greg Underwood, Software Engineering Manager, Yasmine Evjen, Senior Product Manager, Android XR Since introducing the Android XR SDK, developers have transformed their ideas into innovative, immersive experiences for XR headsets and wired XR glasses. As the ecosystem expands, you can more easily take those experiences from preview to production and reach users wherever they are. Today, we're excited to announce that Jetpack SceneCore, ARCore for Jetpack XR, and XR Runtime have reached beta with Jetpack Compose for XR to follow soon! This means the APIs are stabilizing, making it a great time to start integrating them into your production workflows and creating for Android XR. Why the Jetpack XR SDK? The Jetpack XR SDK includes all the tools and libraries you need to build immersive and augmented experiences for Android XR. Whether you're porting an existing 2D app or creating a new 3D XR app from scratch, you can do so using the familiar Android development tools you already know and love. To support your development, this release focuses on providing the fundamental building blocks across the SDK: Jetpack SceneCore: Build and manipulate the Android XR scene graph with 3D content. You can arrange 3D models, play spatial audio, and use the robust entity-component system to create, control, and manage entities. ARCore for Jetpack XR: Bring digital content into the real world with perception capabilities. This library powers depth estimation, persistent anchors, hit testing, and plane identification. XR Runtime: Provides the essential runtime foundation of the SDK, handling device lifecycles, session creation, and system configurations that enable the API surface. Jetpack Compose for XR: Create spatial UI layouts that take advantage of Android XR's spatial capabilities. This library lets you use familiar Compose concepts to create spatial UIs and will be reaching Beta soon. What's new in Beta? Direct feedback from ## How Yandex Cloud built and open-sourced Farm for preview environments DevFeed: [How Yandex Cloud built and open-sourced Farm for preview environments]() Original publisher: [Read original article]() Author: DakEnviy0 (Яндекс, Yandex Cloud & Yandex Infrastructure) Published: 2026-07-30T07:29:36Z Content type: article Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [Docker](), [Kubernetes](), [Self-hosted](), [Development](), [Node.js]() Tags: [dev](), [docker](), [farm](), [frontend](), [js](), [kubernetes](), [node](), [node-js](), [preview](), [preview-87a227230297](), [self-hosted](), [tag-4004cf5948d3](), [tag-92292b2c626f](), [tag-e6d9cc1f0757]() ### AI overview The article describes how Yandex Cloud developed Farm, a service that creates preview environments for pull requests. It traces the system's evolution from a self-hosted script on one virtual machine to an orchestrator using Docker and Kubernetes, and explains the motivation for open-sourcing it. ### Source excerpt Каждый пул-реквест хочется не просто проверить тестами, а показать вживую -- дизайнеру, менеджеру, соседней команде, чтобы все они смогли потыкаться в UI -- порадоваться, понаходить баги -- порасстраиваться. Казалось бы, что сложного: поднял окружение и дал ссылку. Но когда пул-реквесты сыпятся десятками в день, а команд целое множество, "просто поднять окружение" превращается в отдельный инфраструктурный проект. Привет, Хабр! Меня зовут Михаил Гольбах, я ведущий разработчик интерфейсов Yandex Cloud. Уже несколько лет мы с командой развиваем Ферму -- сервис, который поднимает preview-окружение под каждый пулл-реквест. В этой статье расскажу, как Ферма выросла из простого self-hosted-скрипта на одной виртуальной машине в оркестратор на Docker и Kubernetes и почему в итоге мы открыли её код. Читать далее ## Android Studio Quail 4 Canary 2 now available DevFeed: [Android Studio Quail 4 Canary 2 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-07-23T14:08:38Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [releases](), [Release notes]() Tags: [android](), [android-studio](), [channel](), [download](), [macos](), [new-features](), [preview](), [release](), [release-notes](), [update]() ### AI overview Android Studio Quail 4 Canary 2 is available in the Canary channel. Existing Canary users can update through the IDE, while others can download it. The article links to preview release notes and closed issues for more details. ### Source excerpt Android Studio Quail 4 Canary 2 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Quail 4, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Quail 4, see closed issues. ## Multi-Cluster v2 and Stateless Mode now in Preview DevFeed: [Multi-Cluster v2 and Stateless Mode now in Preview]() Original publisher: [Read original article]() Author: Alexander Schwartz Published: 2026-07-17T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authentication](), [Database](), [Availability](), [Replication](), [Kubernetes](), [Amazon Web Services]() Tags: [authentication](), [availability](), [clustering](), [database](), [distributed](), [failover](), [idm](), [kerberos](), [ldap](), [monitoring](), [openid-connect](), [preview](), [replication](), [saml](), [sso]() ### AI overview Keycloak 26.7 introduces Stateless Mode as a preview. It moves volatile data, including authentication sessions, action tokens, and brute-force counters, from Infinispan caches to the database, supporting multi-cluster deployments without an external Infinispan cluster. ### Source excerpt Starting with Keycloak 26.7, the stateless feature is available as a preview. It fundamentally simplifies how Keycloak handles volatile data -- authentication sessions, action tokens, and brute-force counters move from embedded or external Infinispan caches to the database. The result: Keycloak deployments that are easier to operate, more resilient, and ready for multi-cluster setups without an external Infinispan cluster. Read on to learn more, and ask questions in our upcoming live Q&A event on Jul 21! The problem with the current approach A multi-cluster setup becomes necessary when no transparent networking between two sites is available for Keycloak's embedded Infinispan to form a single cluster -- for example, when sites are in different availability zones or data centers without a shared network layer. Running Keycloak in such a multi-cluster setup today requires significant infrastructure beyond Keycloak itself. Without the stateless feature, the architecture depends on an external Infinispan cluster with cross-datacenter replication channels, dedicated monitoring to detect and handle Infinispan failover, and operational procedures for failback. It was tied to specific environments like Kubernetes and AWS, and using it in other environments would require significant work to adapt it. Even in single-cluster deployments, Infinispan clustering introduces operational overhead: rebalancing data in distributed caches when a node is lost or restarted, and transient failures in login flows if a node unexpectedly disappears. In large installations, the login failure cache can grow significantly, consuming substantial memory and causing long rebalancing times when nodes join or leave the cluster. While distributed caches replicate data across at least two nodes -- so individual node failures do not lose data -- a full cluster restart during minor upgrades resets volatile state such as in-progress authentication sessions and brute-force counters. What changes with stateles ## Android Studio Quail 4 Canary 1 now available DevFeed: [Android Studio Quail 4 Canary 1 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-07-16T13:28:23Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Android Gradle Plugin](), [Gradle](), [Emulator](), [Linux](), [macOS]() Tags: [android](), [android-gradle-plugin](), [android-studio](), [emulator](), [gradle](), [linux](), [macos](), [preview](), [release](), [release-notes]() ### AI overview Android Studio Quail 4 Canary 1 is available in the Canary channel. The release includes general fixes and changes involving Android Studio, Android Gradle Plugin, Gradle integration, lint, navigation, and emulator-related behavior. ### Source excerpt Android Studio Quail 4 Canary 1 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Quail 4, see the Android Studio Preview release notes. General fixes and features Below is a list of general fixes in Android Studio Quail 4 Canary 1 and Android Gradle Plugin 9.4.0-alpha05. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues Android Studio Issue #533146818 ExtractAnnotations task does not share build cache entries between mac and linux Gradle Integration Issue #491718901 AGP 9.1.0 Circular dependency error between :app:l8DexDesugarLibUiTest and :app:minifyAndroidTestWithR8 Lint Issue #526716181 Disable DalvikOverride by default Issue #533527424 Lint tasks do not share build cache entries between mac and linux Navigation Editor Issue #271424916 nested navigation graph as starting destination breaks Android Studio Preview Running Devices Issue #532163938 "Hardware Input" emulator option is not persisted across Android Studio restarts ## Android Studio Quail 3 RC 1 now available DevFeed: [Android Studio Quail 3 RC 1 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-07-14T14:02:53Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Beta channel](), [releases](), [Release notes](), [macOS]() Tags: [android](), [android-studio](), [beta-channel](), [macos](), [preview](), [release](), [release-notes](), [update]() ### AI overview Android Studio Quail 3 RC 1 is available in the Beta channel. Existing Beta users can update through the IDE, while others can download it. The article points to preview release notes and closed issues for feature and bug-fix details. ### Source excerpt Android Studio Quail 3 RC 1 is now available in the Beta channel. If you already have an Android Studio build on the Beta channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Quail 3, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Quail 3, see closed issues. ## Android Studio Quail 3 Canary 4 now available DevFeed: [Android Studio Quail 3 Canary 4 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-07-10T05:35:48Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Android Gradle Plugin](), [bug](), [Release notes](), [Gradle]() Tags: [android](), [android-gradle-plugin](), [android-studio](), [bug](), [build](), [crash](), [gradle](), [macos](), [preview](), [release](), [release-notes]() ### AI overview Android Studio Quail 3 Canary 4 is available in the Canary channel. The release includes general fixes in Android Studio and Android Gradle Plugin 9.4.0-alpha04, including a fix for a physical phone crash when using Ctrl+scroll wheel with Running Devices. ### Source excerpt Android Studio Quail 3 Canary 4 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Quail 3, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Quail 3, see closed issues. General fixes and features Below is a list of general fixes in Android Studio Quail 3 Canary 4 and Android Gradle Plugin 9.4.0-alpha04. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues Gradle Issue #485304996 Allow setting android.newDsl=false to an isolated set of projects Running Devices Issue #527843241 Physical phone crash when using CTRL + scroll wheel on Android Studio running devices ## Scale Faster with Managed Weaviate: Now in Public Preview on DigitalOcean DevFeed: [Scale Faster with Managed Weaviate: Now in Public Preview on DigitalOcean]() Original publisher: [Read original article]() Author: Waverly Swinton Published: 2026-07-09T19:08:52Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Cloud](), [Databases](), [Retrieval Augmented Generation (RAG)](), [autoscaling](), [Self-hosted](), [GraphQL](), [gRPC]() Tags: [autoscaling](), [configuration](), [database](), [databases](), [digitalocean](), [graphql](), [high-availability](), [hosting](), [infrastructure](), [preview](), [product-updates](), [real-time](), [rest](), [retrieval](), [run](), [security](), [storage](), [upgrades](), [workflows]() ### AI overview DigitalOcean has placed Managed Weaviate into public preview. The service provides fully managed Weaviate clusters with automated backups, security patching, version upgrades, high availability, and storage autoscaling, with pricing starting at $20 per month. ### Source excerpt Production Weaviate in minutes, managed by DigitalOcean. Starting at $20/month. Vector databases have become a core piece of the AI application stack. Whether you're building retrieval-augmented generation (RAG), semantic search, agentic workflows and memory, or similarity-based recommendations, you need a vector store that's reliable, fast, and doesn't require a dedicated ops engineer to keep running. Weaviate has become a critical part of that stack -- its open-source AI-native vector database powers semantic search, RAG, and agentic workflows for thousands of companies. Self-hosting Weaviate is doable but it comes at a cost. You're on the hook for backups, version upgrades, security patches, high availability configuration, and storage scaling. That's real time and real engineering capacity that isn't going toward your product. Managed alternatives from larger cloud vendors exist, but they often come with per-query fees, per-dimension surcharges, and pricing models that are difficult to predict as usage grows. Today, we're announcing that Managed Weaviate is now in public preview on DigitalOcean, offering an easy way for you to run Weaviate in production, at a price that makes sense from day one. The easiest way to run Weaviate in production Managed Weaviate on DigitalOcean handles the operational work so you don't have to. Provision a fully managed Weaviate cluster directly from the DigitalOcean control panel. From there, automated backups, security patching, version upgrades, high availability, and storage autoscaling are handled for you. Full Weaviate client compatibility via GraphQL, REST, and gRPC on port 443 means your existing code works without modification. This means you get Weaviate's full capabilities -- semantic and hybrid search, RAG pipelines, and support for agent-driven workflows -- without spending engineering time on the infrastructure beneath them. Predictable pricing, starting at $20/month We built Managed Weaviate with flat, predictable monthly ## June developer updates: AI capabilities, releases, projects, and Temporal guidance DevFeed: [June developer updates: AI capabilities, releases, projects, and Temporal guidance]() Original publisher: [Read original article]() Author: Temporal Technologies Published: 2026-06-30T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [releases](), [Strands Agents](), [SDKs](), [Amazon Web Services](), [Cloud](), [Command-line interface](), [Serverless](), [Open Source](), [Python]() Tags: [ai](), [announcements](), [cli](), [cloud](), [community](), [open-source](), [practical](), [pre-release](), [preview](), [python](), [releases](), [scale](), [teams]() ### AI overview A June digest covering Temporal updates, including an AWS Strands Agents integration in public preview, a Cloud CLI extension in pre-release, stable Namespace Endpoint IPs, Custom Roles, and the Temporal OSS v1.31 release. It also highlights live events, community projects, and a Python tutorial. ### Source excerpt Highlights from June include new AI capabilities, major releases, community-built projects, and practical guidance from teams running Temporal at scale. ## Run Codex in the cloud - DigitalOcean for Codex is now available DevFeed: [Run Codex in the cloud - DigitalOcean for Codex is now available]() Original publisher: [Read original article]() Author: Ari Sigal Published: 2026-06-25T21:16:06Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [codex](), [Digital Ocean](), [remote-development](), [Cloud](), [Provisioning](), [ssh](), [ChatGPT]() Tags: [ai-ml](), [cloud](), [codex](), [digitalocean](), [mobile](), [oauth](), [plugin](), [preview](), [product-updates](), [provisioning](), [remote-development](), [ssh]() ### AI overview DigitalOcean announces a Public Preview plugin for Codex that lets developers provision persistent, Codex-ready cloud development machines in their own DigitalOcean accounts using natural-language prompts. The resulting Droplets include the Codex CLI, common programming-language tooling, and SSH access. ### Source excerpt As your agents are working on more complex, long-running work, they need a clean, persistent environment to keep running. Setting up a persistent remote machine by hand means creating a cloud server, configuring SSH keys, installing dependencies, and wiring everything back to your workflow. It's a lot of infrastructure work before you write a single line of code. Today, we're making that easier. The DigitalOcean plugin for Codex is now available in Public Preview, letting developers create and connect Codex-ready cloud development machines in their own DigitalOcean account directly from within Codex -- using natural language, with no manual setup. This means that not only can your work continue running when you step away, but with Codex in the ChatGPT mobile app you can stay in control -- starting, steering, or monitoring work from wherever you are. What is DigitalOcean for Codex? The DigitalOcean plugin connects your DigitalOcean account to the Codex app, letting you provision a persistent remote development environment on demand. Instead of manually spinning up a server and configuring it, you can ask Codex to do it. The result: a DigitalOcean Droplet® that's pre-configured with the Codex CLI, common programming language tooling (based on the codex-universal Docker image), and SSH access -- so your work can keep running and stay within reach, even when you're not at your desk. How it works Starting from Codex Install the DigitalOcean plugin from the Codex plugin directory. During installation, you'll connect your DigitalOcean account via OAuth -- no API tokens to create or paste. Then prompt: @DigitalOcean create a new remote machine Codex will: Provision a new Droplet from the Codex Droplet template Generate and configure an SSH key on your device Wait for the machine to finish provisioning (and check back automatically when it's ready) Return a deeplink to the Codex SSH connections page to finalize the connection Once connected, you're running Codex on a persistent ## Neo code reviews: AI code review built for infrastructure DevFeed: [Neo code reviews: AI code review built for infrastructure]() Original publisher: [Read original article]() Author: Pulumi Neo Team Published: 2026-06-22T15:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [pulumi-neo](), [ai code review](), [Infrastructure as code](), [pull-requests](), [GitHub]() Tags: [ai](), [ai-agents](), [ai-code-review](), [features](), [github](), [governance](), [infrastructure-as-code](), [logging](), [preview](), [product](), [pull-requests](), [pulumi-neo]() ### AI overview Pulumi introduces Neo code reviews in public preview. The feature analyzes GitHub pull requests alongside Pulumi Cloud infrastructure state, preview output, stack relationships, and dependencies to provide high-level and code-level feedback. It supports automatic or mention-triggered reviews, with governance controls including RBAC, guardrails, and audit logging. ### Source excerpt Today we're introducing Pulumi Neo code reviews, now in public preview. Neo code reviews analyze pull request changes in conjunction with what Pulumi Cloud knows about your running infrastructure, providing both high-level and code-level feedback. Normal code review agents can't reliably anticipate the impact an infrastructure-as-code change will have. This is because they don't have access to critical aspects of the IaC workflow: the potential impact the update will have, in this case the pulumi preview output; and the current state of the cloud infrastructure. Neo not only has access to both of those, but also to the entirety of your other cloud context, such as stack relationships and dependencies. Running reviews Neo can review every pull request automatically, or only when someone mentions @pulumi-neo. Either way, it skips draft pull requests and those opened by bots by default. A review is a comment, so it informs the person approving the merge and sits alongside the required checks and branch protection you already enforce. Neo code reviews run inside the same governance as every other Neo task, with the RBAC, guardrails, and audit logging your organization has set. Enable code reviews Neo code reviews are available on GitHub during public preview. They require Pulumi Neo to be enabled for your organization, the Pulumi GitHub App installed on the repositories you want reviewed, and a one-time grant from each organization user to access their GitHub account under Management > Version control. If Neo currently posts preview summaries on your pull requests, code reviews are already enabled, and they take the place of those summaries. Neo code reviews are free while in public preview. On July 1, 2026, they'll be generally available, and reviews will begin counting toward your organization's Neo token usage, at the same per-token rate as any other Neo task. The pricing page shows that rate and the monthly token allotment included with each plan. Give it a try Open ## Android Studio Quail 3 Canary 1 now available DevFeed: [Android Studio Quail 3 Canary 1 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-06-18T15:07:37Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Android Gradle Plugin](), [releases](), [bug]() Tags: [android](), [android-gradle-plugin](), [android-studio](), [bug](), [compose](), [kotlin](), [kotlin-multiplatform](), [preview](), [release]() ### AI overview Android Studio Quail 3 Canary 1 is available in the Canary channel, alongside Android Gradle Plugin 9.4.0-alpha01. The release includes general fixes and features, including fixes for signing configuration, Compose editing, import and sync, Kotlin Multiplatform compilation, running devices, and Cyrillic keyboard input during device mirroring. ### Source excerpt Android Studio Quail 3 Canary 1 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Quail 3, see the Android Studio Preview release notes. General fixes and features Below is a list of general fixes in Android Studio Quail 3 Canary 1 and Android Gradle Plugin 9.4.0-alpha01. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues Android Gradle Plugin Issue #499166350 AGP SigningConfig is too eager Compose Editing Issue #522127451 Android Studio Quail Surround With Widget Option not working Import/Sync Issue #457204879 The Kotlin main() function fails to run with Android Studio Otter (works fine with Narwhal 4) Multiplatform Issue #496002555 androidMain.kotlin.exclude(...) is ignored by compileAndroidMain with com.android.kotlin.multiplatform.library Running Devices Issue #269961652 When using Device Mirroring, Cyrillic keyboard input does not work ## Server-Side Tools Are Now Available for DigitalOcean Inference Engine DevFeed: [Server-Side Tools Are Now Available for DigitalOcean Inference Engine]() Original publisher: [Read original article]() Author: Grace Morgan Published: 2026-06-17T16:33:00Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Inference](), [Artificial Intelligence](), [Model Context Protocol](), [Web](), [Tool](), [real-time]() Tags: [agent](), [agentic](), [digitalocean](), [fetch](), [inference](), [mcp](), [preview](), [product-updates](), [search](), [web]() ### AI overview DigitalOcean announces that Server-Side Tools are available in Public Preview for its Inference Engine. The tools let models use web search, web fetch, DigitalOcean Knowledge Bases, MCP servers, and supported Anthropic and OpenAI tools within inference requests. ### Source excerpt AI applications and agents are only as capable as the tools, data, and systems they can access. With Server-Side Tools, now in Public Preview for DigitalOcean Inference Engine, a model can call out to search the web, read your data, call your systems, and take action all from inside a single inference request. You can enable the new tools with your existing DigitalOcean Model Access Key. No separate tool infrastructure to assemble, no new credentials, no orchestration layer to operate. Server-Side Tools bring web search, web fetch, DigitalOcean Knowledge Bases, MCP servers, and supported Anthropic and OpenAI tools into your inference requests, each covered below. Bring Real-Time Information Into Your AI Applications When applications need current information such as news, documentation, or live data, models can access the web directly during inference. Web Search: Get live answers from the web Web Search enables retrieval of up-to-date information from the web. This enables research workflows, support experiences, and agentic applications that need to reason over recent events, changing information, or content that is not available in a model's training data. Web Fetch: Pull in content from URLs and documents Web Fetch pulls in content from specific URLs or PDFs during inference. It is useful for summarizing pages, extracting structured data from documents, or pulling in reference material on demand. Both Web Search and Web Fetch are powered by Exa. Pricing is usage-based; see the pricing page for current rates. Web Mode: Enable web access through the model URL Some agent frameworks only allow you to configure a model name and do not expose tool configuration. For these cases, DigitalOcean supports Web Mode, which automatically enables Web Search and Web Fetch through the model field. This gives the model access to Web Search and Web Fetch without explicitly defining tools, making it easier to integrate with agent frameworks that only allow model-level configuration ## NFC, Crypto, Biometrics, And A New Build Cloud DevFeed: [NFC, Crypto, Biometrics, And A New Build Cloud]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-22T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Device APIs](), [Framework](), [Cloud](), [Bluetooth](), [Cryptography](), [ui](), [JavaScript]() Tags: [android](), [bluetooth](), [cloud](), [crypto](), [device-apis](), [framework](), [ios](), [javascript](), [nfc](), [preview](), [ui]() ### AI overview This weekly Codename One update covers biometrics, cryptography, and NFC APIs moving into the framework core, a Bluetooth simulator change, and a new Build Cloud UI available as a preview for feedback. ### Source excerpt Device APIs move into the framework core, revolutionary Bluetooth debugging, and the Build Cloud's new UI is live in preview. ## Standalone Activities: Durable job processing, now in Public Preview DevFeed: [Standalone Activities: Durable job processing, now in Public Preview]() Original publisher: [Read original article]() Author: Phil Prasek Published: 2026-05-14T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Job](), [Cloud](), [observability](), [SDKs](), [API](), [Command-line interface]() Tags: [2](), [api](), [backend](), [cli](), [cloud](), [deployment](), [job](), [observability](), [preview](), [product-news](), [retries]() ### AI overview Temporal announces the Public Preview of Standalone Activities, which provide durable background job processing with retries, observability, and lifecycle controls across most Temporal SDKs and Temporal Cloud. ### Source excerpt Temporal Standalone Activities are now in Public Preview, bringing durable job processing, retries, observability, and lifecycle control to Temporal Cloud. [Next page]()