[Sync] 8.2.0 main to develop

[arun-s-aot]

📝 Pull Request Summary

Description:

Related Jira Ticket:

Type of Change:

• ✨ Feature
• 🐞 Bug Fix
• ♻️ Refactor
• 🧹 Code Cleanup
• 🧪 Test Addition / Update
• 📦 Dependency Update
• 📘 Documentation Update
• 🚀 Deployment / Config / Security Updates

---

🧩 Microfrontends Affected

Please select all microfrontends or modules that are part of this change:

• forms-flow-admin
• forms-flow-components
• forms-flow-integration
• forms-flow-nav
• forms-flow-review
• forms-flow-service
• forms-flow-submissions
• forms-flow-theme
• scripts
• Others (please specify below)

Details (if Others selected):

---

🧠 Summary of Changes

---

🧪 Testing Details

Testing Performed:

Screenshots (if applicable):

---

✅ Checklist

• Code builds successfully without lint or type errors
• Unit tests added or updated
• Integration or end-to-end tests validated
• UI verified
• Documentation updated (README / Confluence / UI Docs)
• No sensitive information (keys, passwords, secrets) committed
• I have updated the CHANGELOG with relevant details
• I have given a clear and meaningful PR title and description
• I have verified cross-repo dependencies (if any)
• I have confirmed backward compatibility with previous releases
• Verified changes across all selected microfrontends

---

👥 Reviewer Notes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Release Tag The VERSION file now appears to contain both the new and the previous version values. Confirm whether the release tooling expects a single version string, and ensure the file format matches what CI/CD and deployment scripts parse. v8.2.0-alpha Version Sync Multiple microfrontend package.json files were bumped to 8.2.0-alpha. Validate that all relevant packages that participate in the build/release are updated consistently (including any root/workspace metadata if applicable) to avoid mismatched artifact versions. "version": "8.2.0-alpha", Semver Format Confirm the 8.2.0-alpha pre-release tag format is compatible with your publishing and deployment process (e.g., npm dist-tags, Docker image tags, and any version comparison logic), especially if automation previously relied on 8.1.0-alpha. "version": "8.2.0-alpha",

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Remove duplicate old version line Remove the leftover previous version line so the VERSION file contains a single authoritative version value. Keeping multiple versions in this file can break tooling that expects a single-line version string. VERSION [1-2] v8.2.0-alpha -v8.1.0-alpha Suggestion importance[1-10]: 7 __ Why: The VERSION file in the new hunk contains both v8.2.0-alpha and the previous v8.1.0-alpha, which can break consumers that expect a single version string. Removing the leftover line makes the version source unambiguous and consistent with the bumped package.json versions.	Medium