Updated version from 7.1.0-alpha to 7.2.0-alpha

[vinaayakh-aot]

User description

Issue Tracking

JIRA:
Issue Type: BUG/ FEATURE

Changes

---

PR Type

Enhancement

---

Description

• Bump project version to v7.2.0-alpha

• Update micro-frontends package versions

• Add version-cli configuration file

---

Changes diagram

flowchart LR
  V["VERSION file"]
  C["scripts/version-cli/config.json"]
  P["package.json files"]
  V -- "defines new version" --> C
  C -- "applies version updates" --> P

Loading

---

Changes walkthrough 📝

Relevant files

Configuration changes

10 files VERSION Bump `VERSION` to `v7.2.0-alpha`                                                  +1/-1      package.json Update admin package version to `7.2.0-alpha`                        +1/-1      package.json Update components package version to `7.2.0-alpha`              +1/-1      package.json Update integration package version to `7.2.0-alpha`            +1/-1      package.json Update nav package version to `7.2.0-alpha`                            +1/-1      package.json Update review package version to `7.2.0-alpha`                      +1/-1      package.json Update services package version to `7.2.0-alpha`                  +1/-0      package.json Update submissions package version to `7.2.0-alpha`            +1/-1      package.json Update theme package version to `7.2.0-alpha`                        +1/-0      config.json Add `version-cli` configuration definitions                            +239/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

[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: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Undefined regex pattern The configuration refers to "ff_json_version_pattern" as the find pattern, but it's not defined in this file. Ensure that the regex for ff_json_version_pattern is declared or imported so version replacements actually occur. "find": "ff_json_version_pattern", "replace": "\"version\": \"{{npm_version}}\"", "type": "regex" Inconsistent context settings In the "Forms Flow Service Package" update, the context block omits max_matches, while all other package-lock entries specify it. Consider adding max_matches for consistency and predictable behavior. "context": { "near": "\"name\": \"@formsflow/services\"" } }

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Remove redundant version line Remove the leftover old version line and ensure the file only contains the new version with a trailing newline. This prevents confusion over which version is current. VERSION [1] +v7.2.0-alpha - Suggestion importance[1-10]: 6 __ Why: The duplicate old version line can cause confusion; removing it clarifies the current version.	Low
General	Add max_matches to service context Add a max_matches field to the context for the service package update to mirror other entries and limit unintended replacements. This ensures consistent behavior across all package locks. scripts/version-cli/config.json [156-164] { "description": "Service micro-frontend version", "find": "ff_json_version_pattern", "replace": "\"version\": \"{{npm_version}}\"", "type": "regex", "context": { - "near": "\"name\": \"@formsflow/services\"" + "near": "\"name\": \"@formsflow/services\"", + "max_matches": 2 } } Suggestion importance[1-10]: 5 __ Why: Adding max_matches aligns this entry with others and prevents unintended replacements across contexts.	Low
	Ensure newline at EOF Add a newline at the end of the JSON file to comply with POSIX standards and avoid issues with tools expecting an EOF newline. scripts/version-cli/config.json [239] +} - Suggestion importance[1-10]: 2 __ Why: An end-of-file newline is a minor POSIX compliance improvement with minimal impact on functionality.	Low