---
title: "Release notes 4 September 2025"
canonical: "https://support.appfire.com/space/CT/2331738113/Release%20notes%204%20September%202025"
format: markdown
---
> Macro (aura-html)

**Release date**: 9/4/2025 

Our team is thrilled to announce the latest release of Composition Tabs for Confluence Cloud.

**AC version**: 6.0.0

---

# Update about Legacy TabsGroup Macros in Confluence cloud editor

---

## Overview

The pages migrated from DC to Cloud retain the legacy editor on the cloud. The Composition Tabs app is now fully “Runs on Atlassian” as a Forge app. The apps moved to Forge do not render macros in the legacy editor. The following article details how to work with legacy macros. 

## TL;DR

**Convert and close. Do not click “Update” on pages with nested macros.**

## Forge Macros in the Legacy Editor

- Forge macros **do not render** in the legacy editor.
- When a page contains a Forge macro, a **placeholder message** is displayed instead of the macro.

![image-20250903-171144.png](media://68be64e0-04fc-4698-a39a-94164034b1cd)

 

📌 **Note**: To view the content, you must convert the page to the cloud editor.

---

## Editing a Page in the Legacy Editor

When you attempt to edit a page with a Forge macro:

1. Confluence will display a **prompt to convert to the new editor**.
2. Click **Convert** to proceed.
3. Once converted, the Forge macro will render correctly.

![image-20250903-171220.png](media://cf80e655-30d5-4bf6-a8b3-fdd4db3471b0)

 

---

## Working with the Cloud Editor (Most Important)

- Tabs Group Macro is a nested macro. In the cloud editor, **nesting of macros is not supported**.
- If you click **Update** while editing a nested macro (e.g., Tabs), the **tab content will be lost**.

✅ **Recommended Action**:

- Do **not** click **Update** in this scenario.
- Instead, simply **close the editor** to return to the page.
- On closing, the page will display the content correctly.

![image-20250903-171305.png](media://fee8a4d7-c0c4-4d36-97bb-7a917e346a57)

 

 

---

## Converting Legacy Macros to the New Tabs Macro

At this point, you can choose to retain the legacy Macro and stop here. If you decide to move to the Cloud editor-supported Tabs Macro, you can continue with this step.

If your page contains a **legacy TabsGroup macro**:

1. A **deprecation notice** will appear on the macro.
2. The notice includes a **Switch to Tabs** button.
3. Click **Switch to Tabs** to convert the legacy macro to the new **Tabs macro**.

![image-20250903-171459.png](media://ca4989a2-92db-417c-bc3e-d29cdb4c31ed)

 

---

## After Conversion

- The page will now display the content inside the new **Tabs macro format**.
- All existing content is migrated into the new structure.

![image-20250903-171517.png](media://861c340a-0adb-4887-a169-82ac77dbad3a)

 

---