update release notes

Author: Slashek

app/views/pages/developer-guide/platformos-workflow/directory-structure/config.liquid

@@ -25,6 +25,7 @@ metadata:
 |safe_translate                                                  |true|If disabled, the `translate` filter (`t` is an alias for it) will mark the output as html_safe. This can lead to XSS vulnerability, if you provide user input as a variable, as it could contain malicious JavaScript. In such scenario, you should explicitly use another filter, `translate_escape` (or `t_escape`). However, by keeping this flag as `true`, the system will automatically use the equivalent of `t_escape` if you provide any variable to the translation key, making your application safer by default. We highly recommend keeping this flag to `true`.|
 |skip_elasticsearch                                              |false|If you do not use the `keyword` argument in `records`/`users` queries or `customizations`/`people` queries, you can increase performance by avoiding indexing data in the ELasticSearch by setting this flag to `true`.|
 |slug_exact_match                                                |true|If disabled, a page with slug `abc` will match not only  `example.com/abc`, but also URLs like `example.com/abc/1`, `example.com/abc/1/x` and to control this behavior, you would need to set [max_deep_level Page property](/developer-guide/pages/pages#available-properties). By keeping this flag as true, only `example.com/abc` will be matched. Additionally, you will be able to use named parameters in the URLss, like /abc/:id. We highly recommend setting this flag to true.|
+|string_interpolation                                            |false|When enabled, allows using {% raw %}`{{ }}`{% endraw %} syntax inside double-quoted strings for variable interpolation (e.g., {% raw %}`{% assign greeting = "Hello {{ name }}!" %}`{% endraw %}). This provides a more readable alternative to filter chains. **Note:** Enabling this is a breaking change if you have existing templates with double-quoted strings containing literal {% raw %}`{{ }}`{% endraw %} text - use single quotes for literals instead. We recommend enabling this for new projects.|
 |sync_assets                             |false|If enabled, with each deploy we will ensure that the state of `admin_assets` matches assets that were listed in the asset manifest, that is generated by pos-cli during pos-cli deploy.
 |sync_translations                             |false|If enabled, translations will be synchronized on each sync/deploy similarly to other resources, meaning if you remove a translation form a translation file and sync it, it will disappear from the Instance. It will also remove all translations from the deleted file. The default behaviour (for backwards compatibility) is that translations will not be deleted; in order to delete a translation one needs to explicitly call `admin_translation_unset` GraphQL mutation. This setting is compatible with `modules_that_allow_delete_on_deploy`.
 |translation_keys_to_ignore                             |[]|Allows to list translation keys which will not be updated/delete on sync/deploy. It is most useful if you would like to change translations using UI and will not reflect it in your codebase. Translations will still be created if not defined.
@@ -46,6 +47,7 @@ require_table_for_record_delete_mutation: true
 safe_translate: true
 skip_elasticsearch: true
 slug_exact_match: true
+string_interpolation: true
 sync_assets: true
 sync_translations: true
 websockets_require_csrf_token: true

app/views/pages/release-notes/unreleased.liquid

@@ -9,13 +9,65 @@ metadata:
 
 #### {{ page.metadata.description }}
 
-<!--<h4 class="release-note release-note__new">NEW</h4>-->
+<h4 class="release-note release-note__new">NEW</h4>
+
+* **String interpolation in double-quoted strings**: You can now use `{{ }}` syntax inside double-quoted strings for cleaner, more readable variable interpolation. This feature is **disabled by default on existing instances** to prevent backwards compatibility issues, but **enabled by default on new instances**. To enable on an existing instance, add to your `config.yml`: `string_interpolation: true`
+
+  **Example:**
+  ```liquid
+  {% raw %}
+  {% assign name = "Alice" %}
+  {% assign greeting = "Hello {{ name | upcase }}!" %}
+  {{ greeting }}
+  {% endraw %}
+  ```
+  **Output:** `Hello ALICE!`
+
+  **Features:**
+  * Works with variables, property access, array access, and filters
+  * Supports filter chains: {% raw %}`"{{ name | upcase | truncate: 10 }}"`{% endraw %}
+  * Multiple interpolations: {% raw %}`"{{ first }} {{ last }}"`{% endraw %}
+  * Works in all tags that accept string values (assign, function, background, export, log, etc.):
+    ```liquid
+    {% raw %}
+    {% assign var = "world" %}
+    {% log "hello {{ var }}" %}
+    {% assign greeting = "hello {{ var }}" %}
+    {% function res = "lib/func", arg: "hello {{ var }}" %}
+    {% endraw %}
+    ```
+
+  **Important notes:**
+  * Single-quoted strings never interpolate (use for literal `{{ }}` text)
+  * **Breaking change if enabled:** Existing templates with double-quoted strings containing literal {% raw %}`{{ }}`{% endraw %} text will now interpolate. Use single quotes for literal text: {% raw %}`'Use {{ variable }} syntax'`{% endraw %}
 
 <h4 class="release-note release-note__improved">IMPROVED</h4>
 
 * **Upgraded internal dependencies** for improved performance and security
+* **Upgraded GraphQL gem to the latest version** for security and performance
 * **Clearer error messages for `record_update` and `record_destroy`**: When a record with the provided ID cannot be found, the error message now clearly specifies which table was being searched. For example:
   * Before: `Couldn't find Customization with 'id'=123`
   * After: `Can't find Boats with id=123`
+* **`assign` tag now supports hash/array operations directly**: The `assign` tag has been extended with capabilities previously only available through `hash_assign` (which is now deprecated). You can now use a single, unified syntax for all variable assignments, including initializing hash and array:
+  * **Empty hash/array literals**: {% raw %}`{% assign foo = {} %}`, `{% assign bar = [] %}`{% endraw %} (no need to do {% raw %}`'{}' | parse_json`{% endraw %} anymore)
+  * **Inline hash/array literals with values**: You can now create hashes and arrays with initial values directly in the assign tag. Variables are evaluated, and can be used both as values and as keys:
+    ```liquid
+    {% raw %}
+    {% assign var = "hello" %}
+    {% assign hash = { "key": var, var: "value", arr: ["el1", var] } %}
+    {{ hash }}
+    {% endraw %}
+    ```
+    **Output:** `{ "key": "hello", "hello": "value", "arr": ["el1", "hello"] }`
+  * **Bracket notation**: {% raw %}`{% assign foo["bar"] = "baz" %}`{% endraw %}
+  * **Dot notation**: {% raw %}`{% assign foo.bar = "baz" %}`{% endraw %}
+  * **Mixed notation** (combining dots and brackets): {% raw %}`{% assign foo.bar["baz"] = "qux" %}`{% endraw %}
+  * **Array append with `<<`**: {% raw %}`{% assign foo << 'bar' %}`{% endraw %} (no need to use `array_add` filter)
+  * **Nested operations**: Full support for deeply nested hash and array assignments, e.g., {% raw %}`{% assign foo["bar"]["baz"]["qux"] = [] %}{% assign foo["bar"]["baz"]["qux"] << "first" %}`{% endraw %}
+  * **Performance**: Key lookups are pre-computed at parse time for faster rendering
+* **`function` tag now supports the same hash/array syntax**: Bracket notation, dot notation, mixed notation, and array append with `<<` now work with `function` too:
+  * {% raw %}`{% function foo["bar"] = 'partials/compute', input: 'baz' %}`{% endraw %}
+  * {% raw %}`{% function foo.bar["baz"] = 'partials/get_name', id: 123 %}`{% endraw %}
+  * {% raw %}`{% function foo << 'partials/fetch_item', id: 1 %}`{% endraw %}
 
 <!-- <h4 class="release-note release-note__fixed">FIXED</h4> -->