> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/release-notes/2026/may/akinon-release-notes-05.11.2026.md). # Akinon Release Notes (05.11.2026) ## Omnitron {% hint style="warning" %} The following changes are available in **Omnitron FE versions later than `v3.8.0` and Omnitron BE versions later than `v1.4.1`.** {% endhint %} #### Resolved Issues **Marketplace Attribute Required Labels** * An issue causing incorrect visibility of required field labels for marketplace attributes in Mapper has been resolved. The UI now correctly reflects whether an attribute is marked as required, helping users configure marketplace mappings more accurately and reducing potential validation issues during integration processes. #### New Features **AI Powered Search Time Range Filter** * A new **Time Range** filter has been introduced on the AI Powered Search **Search Results** page to provide more flexible and targeted result analysis. The filter allows users to narrow down search results based on predefined time intervals, with the default selection set to **Last 1 Day**. Supported time range options include: * Last 1 Minute * Last 5 Minutes * Last 1 Hour * Last 1 Day * Last 1 Week * Last 1 Month #### Enhancements **Dynamic Collection Price List Filter** * A new **Price List** filter has been added to the **Dynamic Collection** detail page to improve collection preview and filtering capabilities. The filter dynamically lists the extra price lists associated with the selected catalog, allowing users to easily switch between different pricing contexts. Once a price list is selected, the collection results are automatically filtered according to the related pricing data, enabling more accurate collection validation and management. **Complex Mapping Schema Rendering** * The issue preventing complex mapping schemas from being rendered correctly in the Mapper UI has been fixed. Mapper now successfully supports the rendering of nested and more advanced schema structures, improving visibility and usability for users working with complex mapping configurations. **Awaiting Substitute Order Status Support** * Support for the `430` order status code has been added across all Omnitron services to fully cover the **Awaiting Substitute** order status. With this update, services throughout the Omnitron ecosystem can now consistently recognize and process orders in the Awaiting Substitute state, ensuring improved compatibility and status handling across integrations and workflows. **Sorting UI Improvements** * Several UI enhancements have been implemented in the **Catalogs > Sorting > Preview / Edit** tab to improve the usability and readability of sorting configurations. These improvements provide a more streamlined editing experience, making it easier to preview sorting rules, review configurations, and manage sorting behaviors more efficiently. *** ## Commerce {% hint style="warning" %} The following changes are available in **Commerce versions as of May 11, 2026.** {% endhint %} #### **Resolved Issues** **CRM Gateway Configuration Resilience** * Modified the CRM synchronization task to safely handle environments where the CRM gateway is not actively configured. This prevents repetitive background task failures and significantly reduces unnecessary system error logs. **Email Template Validation Integrity** * Background tasks now handle invalid email templates safely instead of failing. Disabled templates are now skipped safely, so checkout and notification queues keep running without false error alerts. **Retail Store Filter Assertion Fix** * Resolved an assertion error within the retail store API endpoint triggered when filtering by specific store types. The related filter logic was updated with proper queryset definitions, ensuring stable and error-free location filtering for end-users. **Store Group Relation Assignment Correction** * Fixed a type error occurring during retail store group updates caused by direct assignments to reverse relationships. The system now uses appropriate relational manager methods to safely apply or clear store associations. **Category Path Concurrency Handling** * Implemented robust retry mechanisms to handle integrity errors caused by simultaneous category creation requests. The system now safely manages concurrent path generations during bulk catalog synchronizations without returning unhandled database constraint violations. **Basket Item Index Review** * Analyzed database indexes for basket items. Confirmed that existing composite indexes efficiently handle large cart queries. This removes the need for extra standalone indexes, which would increase database storage costs. **Order Registration Transaction Scope Adjustment** * Modified the user registration flow during checkout to ensure that external email provider timeouts or failures do not roll back the entire payment and order creation transaction. User accounts and orders are now successfully created even if the welcome email fails to send. **Product Selection Query Fix** * Resolved a value error triggered by improperly formatted query strings on product detail pages. The service now validates parameters before running database filters, so product variants load without crashes. **Product Detail Attribute Set Validation** * Fixed an attribute error occurring on product detail endpoints when inactive or missing products were queried. The view layer now strictly validates product existence before attempting to retrieve associated attribute configurations, returning proper "Not Found" statuses instead of system errors. **Search Cache Memoization Fix** * Resolved a parameter conflict within the search service caching mechanism that caused failures during search result generation. The memoizer utility was refactored to safely handle keyword arguments without overlapping function signatures. **Optimistic Concurrency Control for Cart Merging** * Implemented safe retry logic for cart merging operations during user authentication. The system now handles optimistic locking conflicts when multiple concurrent login requests attempt to modify the same user session. **Installment Filter Value Conversion** * Fixed a value error in the installment filtering logic that occurred when decimal formats were passed instead of integers. The filter now safely converts float strings to integers, ensuring accurate payment option displays on product pages. **Product Converter Offer Batching** * Resolved an N+1 performance issue in the product conversion background task. Basket offer checks are now batched correctly, which greatly reduces repeated database queries when processing product lists. **CRM Entity Mapping Type Fix** * Fixed a type error within the CRM entity mapping service caused by unexpected integer values. All mapping parameters are now converted to strings before combining them, ensuring data syncs to external systems without errors. **Configuration Parsing Resilience** * Resolved a JSON decoding error within the frontend configuration processor. The service now manages unexpected non-JSON responses from internal endpoints, preventing frontend rendering failures when fetching environment variables. #### **New Features** **AI Suggestions Bulk Processing & Caching** * Redesigned the AI-powered search suggestion engine to use bulk processing and improved caching. By combining AI requests and reusing cached facet data, suggestion generation time dropped from minutes to seconds. **AI Suggestions Rule Set Optimization** * Refactored the AI Suggestions logic to prioritize the most frequently searched keywords dynamically, removing overly complex legacy filtering rules. The system now seamlessly converts high-volume searches directly into user suggestions, enhancing search relevance. *** ## OMS {% hint style="warning" %} The following changes are available in **OMS versions later than `oms724`**. {% endhint %} #### **Resolved Issues** **Manual Reservation Correction Task Stability** * An issue causing the periodic task responsible for correcting manual reservation entries to fail mid-run has been resolved. The task now safely skips orphaned reservation actions and processes the remaining records reliably on every run, ensuring that reservation corrections are no longer interrupted. #### **Enhancements** **Replacement Product Handling After Additional Payment** * The replacement product workflow has been improved to handle scenarios where additional customer payment is required. When the additional payment is completed in Omnitron, OMS now receives the replacement webhook automatically, updates the relevant package with the replacement item, and publishes the corresponding domain event eliminating the need for manual operational follow-up. **Blacklist Functionality Extended to Accepted Packages** * The blacklisting action, used to mark an item as out-of-stock and trigger replanning, was previously only available for packages in waiting state. It now also works for packages in accepted state, giving operations teams greater flexibility to manage stock issues at later stages of the fulfillment flow. **Automated Cleanup of Old Blacklist Records** * A new periodic task has been introduced to automatically clean up Blacklist Product records older than a configurable retention period. The retention duration is managed through Application Settings, eliminating the need for manual table maintenance and keeping blacklist data current. **Order Search by Tracking Number** * The order search API now supports filtering by tracking number in addition to order number and easy return code. This makes it faster for operations and integration teams to locate an order when only the cargo tracking number is on hand. **Configurable Staff Creation Email** * The welcome email sent when a new staff account is created can now be enabled or disabled per environment via Application Settings. This is particularly useful for setups where staff onboarding is managed outside of email notifications. *** ## Instore {% hint style="warning" %} The following changes are available in Instore FE versions later than `acc-834` and Instore BE versions later than `s157.` {% endhint %} #### New Features **Optional National Short Address in Checkout** * The "National Short Address" field in the checkout flow, previously enforced as mandatory by default, has been changed to optional. Staff can now proceed with checkout without entering a short address code, while the field remains available for cases where the information is provided. Validation still applies when a value is entered. **Order Search by Tracking Number on Refund** * The Instore refund screen now supports searching for orders by cargo tracking number, in addition to the existing order number search. This is particularly useful for return scenarios such as Trendyol returns where the brand only has the cargo tracking code on hand and not the original order number. Once located via tracking number, the refund process continues through the standard flow. **Staff Selection Screen Display by Seller Code Only** * The staff selection screen used at the start of a sales session can now be configured to display only the seller code, hiding staff names. This option has been activated for the Intersport tenant and helps prevent staff-mismatch errors by ensuring each user selects their own seller code rather than a name. Tenants that do not enable this option continue to see the existing name + seller code layout. **Basket Discount Display for Group Product Pricing** * The product detail page now displays basket campaign pricing for group products (e.g. furniture sets). For each item in a group product, if a basket discount applies, a "Sepette X ₺" label is shown in green directly beneath the regular price. A strikethrough total at the top of the page reflects the sum of the discounted prices across all items, while the original total is displayed alongside it. All amounts are formatted according to the active locale's thousand and decimal separators, ensuring consistent price presentation across markets. *** ## Seller Center {% hint style="warning" %} The following changes are available in **Seller Center FE versions later than `v.08.133` and Seller Center BE versions later than `v1.1.179f1`.** {% endhint %} #### Resolved Issues **Revision Request Status Display Fix** * Fixed an issue where revision request statuses were not displayed accurately on the frontend. Previously, both "Approved" (status 2) and "Published" (status 5) were shown as "Approved," causing confusion. All revision statuses: Draft, Submit, Approved, Rejected, Publishing, Published, and Auto Approving are now displayed correctly. Additionally, the status filter has been updated to include all available statuses. ![](/files/c7GoOUlEfRZsnvqijFnC) #### New Features **Billing Address in Package Detail** * Sellers can now see the Billing Address directly on the **Package Detail** page. Previously this was only available on the **Order Detail** page, so you no longer need to navigate back to the order to check invoice details. ![](/files/fDq74bZo27bkHjUI4piV) **Offer Actions Page Improvements** * Sellers can now modify attributes on **Rejected Offers** via **Products > Offer Actions > Rejected > Offer Actions** before performing the resolve action, allowing corrections to be made directly without additional steps. ![](/files/9wcxVZArreZQ2bOyWtxE) * The system now sends the rejection reason explanation in the **Rejected Offers** via **Products > Offer Actions > Rejected Offers** page instead of the rejection reason code for improved clarity. ![](/files/ij9HW3r9G0HJ9zgGrVbK) * Additionally, on **Pending Offers** in **Products > Offer Actions > Pending Offers > Offer Actions**, sellers can now change the linked product. A **Detach Product** button has been added to allow sellers to detach the related product by setting the product field to null. ![](/files/nouNFMlskxXM7oWSb09S) *** ## App Maker {% hint style="warning" %} The following changes are available in **App Maker Environment version `env6.7.0`.** {% endhint %} ### Mobile #### New Features #### React Native React and Expo SDK Upgrade React Native has been upgraded to `0.81` and React has been upgraded to `19.1.4`. *** #### **Android Toolchain Update** * Android build tooling has been updated to align with the new React Native `0.81` baseline: \- `compileSdk`, `targetSdk`, and `buildTools` updated to `36` \- Kotlin updated to 2.1.20 \- Gradle updated to 8.14 \- android/app/src/debug/AndroidManifest.xml has been removed (no longer required) {% hint style="warning" %} **Google Play's Target API Level Requirement** **Starting August 31 2026,** new apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play You will be able to request an extension to November 1, 2026 if you need more time to update your app. You'll be able to access your app's extension forms in Play Console later this year. {% endhint %} *** #### **Expo SDK 54** Expo SDK has been updated to 54. All Expo-based modules used by the framework have been updated to versions compatible with SDK 54. envVersion 6.7.0 is sufficient, no additional configuration is required. The following Expo modules have been updated: * expo-apple-authentication 8.0.8 * expo-auth-session 7.0.10 * expo-constants 18.0.13 * expo-crypto 15.0.8 * expo-font 14.0.11 * expo-image 3.0.11 * expo-keep-awake 15.0.8 * expo-linear-gradient 15.0.8 * expo-linking 8.0.11 * expo-localization 17.0.8 * expo-screen-orientation 9.0.8 * expo-secure-store 15.0.8 * expo-status-bar 3.0.9 * expo-web-browser 15.0.10 * expo-navigation-bar 5.0.10 * @expo/vector-icons 15.0.3 {% hint style="warning" %} **Final Legacy Architecture Release** Expo SDK 54 is the last Expo release that includes Legacy Architecture support. React Native 0.80 introduced a code freeze on the Legacy Architecture, and starting with React Native 0.82 it will no longer be possible to opt out of the New Architecture. The next Expo SDK (expected to ship with React Native 0.83) will only support the New Architecture. A growing number of libraries already require the New Architecture for example, react-native-reanimated v4 and @shopify/react-native-flashlist v2. The React Native interop layer will remain in place for the foreseeable future, which means most Legacy Architecture libraries continue to function inside New Architecture apps. **If you are still on env6.x, plan your migration to env7.x (New Architecture) ahead of the next stack upgrade. Future React Native and Expo SDK upgrades beyond env6.7.0 will be delivered exclusively through env7.x.** **env6.7.0 is the final React Native and Expo upgrade for the env6.x line.** {% endhint %} *** #### **Node.js Minimum Version** * The minimum required Node.js version is now `20.19.4`(the latest Maintenance LTS version at the time of writing) or higher. Builds will fail on older `Node.js` versions. Update your local environment. *** #### **Xcode Minimum Version** The minimum required Xcode version is now `16.1.` iOS builds will fail on older Xcode versions. Make sure the xcodeVersion field in your `akinon.json` file is set to a supported value (16.1, 16.2, or 26.2). *** #### **SafeAreaView Deprecation** The built-in SafeAreaView component from react-native is now deprecated and will be removed in a future version. The framework provides a SafeArea element under @elements that should be used instead. If you are importing `SafeAreaView` directly from react-native via `_dependencies`: 
- import { ReactNative } from '_dependencies';
 - const { SafeAreaView } = ReactNative;
 + import { SafeArea } from "@elements";
If you are importing `SafeAreaView` from @elements: ```javascript - import { SafeAreaView } from "@elements"; + import { SafeArea } from "@elements"; ``` **Action Required** * Update `Node.js` to `20.19.4` or later. * Ensure the Xcode version installed on your machine is `16.1` or later, and that the xcodeVersion field in `akinon.json` matches a supported value. * Replace any usage of `SafeAreaView` (from either react-native or @elements) with the `SafeArea` element from @elements. * Update any plugins listed below that are used in your project to their `6.7.0` versions. * Test all screens, navigation flows, and native modules on both Android and iOS after upgrading. * Begin planning your migration to env7.x (New Architecture). env6.7.0 is the final React Native and Expo upgrade on the env6.x line, and the next Expo SDK will only support the New Architecture. *** #### Plugin Updates If your project uses any of the following plugins, you must update them to the 6.7.0 version to remain compatible with env6.7.0. * akinon-expo-camera 6.7.0 * expo-camera package has been updated to 17.0.10. * akinon-expo-av 6.7.0 * expo-av package has been updated to 16.0.8. Note that expo-av is deprecated by Expo and will be removed in future updates. It is no longer recommended for new development migrate to akinon-expo-video or akinon-rn-video where possible. * akinon-expo-video 6.7.0 * expo-video package has been updated to 3.0.16. * akinon-expo-local-auth 6.7.0 * expo-local-authentication package has been updated to 17.0.8. * akinon-expo-location 6.7.0 * expo-location package has been updated to 19.0.8. * akinon-expo-media-library 6.7.0 * expo-media-library package has been updated to 18.2.1. * akinon-rn-video 6.7.0 * Resolved an Android TextureView issue affecting certain video playback scenarios. The following plugins received a version bump to 6.7.0 for compatibility with the new stack. No behavioral changes: * akinon-rn-picker * akinon-react-native-maps * akinon-snapshot-prevention * akinon-barcode-generator * akinon-sentry * akinon-rn-google-signin * akinon-image-picker * akinon-fbsdk-plugin * akinon-react-native-huawei-map **Action Required** * Review the plugin list in your project and update every plugin you depend on to its 6.7.0 version. * If your project still uses akinon-expo-av, plan a migration. The expo-av module will be removed in a future Expo SDK release. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.akinon.com/release-notes/2026/may/akinon-release-notes-05.11.2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.