UIDATIMP-1669: Bump stripes to v9.2.0 for Ramsons

[OleksandrHladchenko1]

Purpose

• Bump stripes to v9.2.0 and all stripes related modules for Ramsons release.

Links

UIDATIMP-1669

[github-actions]

Jest Unit Test Statistics

       1 files  ±0     225 suites  ±0   11m 8s ⏱️ -12s
1 256 tests ±0  1 251 ✔️ ±0  5 💤 ±0  0 ❌ ±0 
1 267 runs  ±0  1 262 ✔️ ±0  5 💤 ±0  0 ❌ ±0 

Results for commit c916872. ± Comparison against base commit 27c86f5.

♻️ This comment has been updated with latest results.

[zburke]

Technically bumping a peer is always a breaking change since you are stating a new external requirement. If your tests will pass with stripes-* dev-deps pinned to their stripes v9.1 versions, i.e. this app does not require any of the new features added to stripes in v9.2, you can leave the peer-dep and this repo's major version as-is and this PR is unnecessary.

Alternatively, if you choose to keep the new 9.2.0 requirement in peer-deps, then you need to bump this repo's version from 7.1.8 to 8.0.0.

[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 SonarCloud

[OleksandrHladchenko1]

Technically bumping a peer is always a breaking change since you are stating a new external requirement. If your tests will pass with stripes-* dev-deps pinned to their stripes v9.1 versions, i.e. this app does not require any of the new features added to stripes in v9.2, you can leave the peer-dep and this repo's major version as-is and this PR is unnecessary.

Alternatively, if you choose to keep the new 9.2.0 requirement in peer-deps, then you need to bump this repo's version from 7.1.8 to 8.0.0.

Hi @zburke We decided to keep the new 9.2.0 version of stripes in peerDependencies. Therefore we bumped the major version of ui-data-import.