7.0 clean packages

[GeorgeCatalinStan]

updated packages based on tickets : #435 / #436 / #449 / #447 / #452

[github-actions]

Qodana for JS

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[github-actions]

Qodana for JS

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 38.53%. Comparing base (7f47248) to head (6ab15ba).

Additional details and impacted files

@@            Coverage Diff            @@
##                7.0     #462   +/-   ##
=========================================
  Coverage     38.53%   38.53%           
  Complexity      925      925           
=========================================
  Files           169      169           
  Lines          3768     3768           
=========================================
  Hits           1452     1452           
  Misses         2316     2316           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[alexmerlin]

@arhimede I merged #461 and fixed the conflicts it caused - the Asset builder failures are now fixed.
The failing CI actions seem to be caused by some OS-level package updates that we cannot control on our end.

I triggered a test run to confirm that the errors are not caused by the changes in this PR.

[arhimede]

@alexmerlin let's merge everything and see the update instructions