3.20.20

🏠 New home page:

• a28cd97: Prepare base layout for a new home, hide new home page under a feature flag by @poulch
• 3f2ca21: The onboarding state is now stored in user metadata, which means that the onboarding state is persisted between logins on different machines by @poulch
• 24691c4: Rename newHome to wecomePage to allow seamlessly removing a feature flag by @poulch
• 13f63c2: The new home page layout is now responsive, which means that the layout adjusts to desktop, tablet and mobile devices by @poulch
• 67687b3: User onboarding steps are now checking when the user does the required actions by @poulch
• e947997: E2E tests are now updated for the new home page meaning that they don't fail when the new home page is enabled by @Cloud11PL
• 18a4eae: The activity section on the home page now has uniform padding with header, stock and sales by @Cloud11PL
• 0c2971b: Add integration test for new home sidebar by @poulch
• f9130c4: You can now see an onboarding component that guides the user through Saleor Dashboard features by @Cloud11PL
• 9cd4da2: You can now see a new sidebar with analytics and activities by @poulch
• 6990b1e: The new home page with onboarding is now enabled, the old home page code has been removed by @poulch
• e48622c: The test set now includes tests for the welcome page onboarding component by @Cloud11PL
• 8bc92e3: You can now see information tiles regarding Saleor Docs, community, and technical help on the home page by @Cloud11PL
• 7250d03: Padding under home page tiles is now increased to prevent clipping by @Cloud11PL
• a40691f: Environments created via Saleor Cloud now identify and report to PostHog. This means Dashboard now sends telemetry data regarding home page onboarding steps and links by @Cloud11PL
• c40fdf7: Add environment variables to GitHub Workflow to control when to show onboarding for new users by @poulch

🍇 Improvements:

• d677431: Now the list app page shows a footer that allows the user to submit a demanded app by @andrzejewsky

⚙️ Maintenance:

• da3e53b: Removed unnecessary expect that was waiting for the success banner, as it was causing delays on CI. Instead, the test relies on other assertions to verify that changes have been applied by @michalina-graczyk
• 479ae66: Merged expectSuccessBannerMessage and expectSuccessBanner into a single method, removed the redundant method, and updated tests to use the new unified method by @michalina-graczyk
• f1e5f34: Enhanced success banner verification in basePage.ts by adding network idle state check and parallel assertions, while modernizing array operations in shipping methods tests using spread syntax instead of .concat() by @michalina-graczyk
• fab4b4e: Refactored tests by replacing direct banner visibility checks with expectSuccessBanner().
  Removed unnecessary waitForNetworkIdleAfterAction wrappers.
  Simplified test scope for staffMembers and removed explicit timeouts where appropriate by @michalina-graczyk
• 981a0bc: Removed waitForNetworkIdleAfterAction and replaced it with a direct navigation call.Added blur actions on metadataKeyInput and metadataValueInput to ensure input stability before saving in the scope of SALEOR_128 by @michalina-graczyk
• d9600ab: Removed waitForNetworkIdleAfterAction and added direct element waits to ensure readiness before actions by @michalina-graczyk
• 4d9d127: Adjust inline discount test for precise floating-point comparison with .toFixed(2) by @michalina-graczyk