🚀 Pre-release master -> staging_Eisbock5

[YuryHrytsuk]

What kind of pre-release?

master branch

Sprint Name

Eisbock

Pre-release version

5

Commit SHA

d5d06eec4b03853dcab97eb4f318dc16cc890722

Planned date

Thursday, September 13, 2024

Did the commit CI suceeded?

• The commit CI succeeded.

Motivation

• Weekly staging release

What Changed

• ✨ [Frontend] New product: TIP lite 🚨 by @odeimaiz in ✨ [Frontend] New product: TIP lite 🚨 #6346
• 🐛 Fixes catalog's synchronization background task continues errors due to faulty service info by @pcrespov in 🐛 Fixes catalog's synchronization background task continues errors due to faulty service info #6344
• 🎨 add running_time_in_hours to /services/-/aggregated-usages by @matusdrobuliak66 in 🎨 add running_time_in_hours to /services/-/aggregated-usages #6350
• Added some fallback icons for apple devices by @jsaq007 in Added some fallback icons for apple devices #6351
• 🎨 [Frontend] Workspaces: Improve tree I by @odeimaiz in 🎨 [Frontend] Workspaces: Improve tree I #6349
• 🐛 [Frontend] Move to folder by @odeimaiz in 🐛 [Frontend] Move to folder #6355
• 🐛 fix issue with workspace permissions by @matusdrobuliak66 in 🐛 fix issue with workspace permissions #6354
• 🎨 [Frontend] Credits summary: Show time by @odeimaiz in 🎨 [Frontend] Credits summary: Show time #6356
• 🎨 Adds new progress bar to track starting software by @GitHK in 🎨 Adds new progress bar to track starting software #6353
• 🐛 [Frontend] Folders tree: Fixes I by @odeimaiz in 🐛 [Frontend] Folders tree: Fixes I #6358

Devops check ⚠️ devops

• REQUIRED: fix traefik labels on Dalco STAG after release (🚀 Pre-release master -> staging_Eisbock3 #6289 (comment))

e2e testing check 🧪

No response

Summary 📝

• make release-staging name=<sprint_name> version=<version> git_sha=<commit_sha>
  • https://github.com/ITISFoundation/osparc-simcore/releases/new?prerelease=1&target=<commit_sha>&tag=staging_<sprint_name><version>&title=Staging%20<sprint_name><version>
• Draft pre-release
• Announce (add redis key maintenance in every concerned deployment)

  {"start": "2023-02-01T12:30:00.000Z", "end": "2023-02-01T13:00:00.000Z", "reason": "Release ResistanceIsFutile9 "}

• Announce release in Mattermost

  :loud_sound:  Maintenance scheduled for **NAMED_DAY DD. MM from START_TIME - END_TIME**.
  =========================================================================
  
  @all Be aware that you will automatically be logged out and your projects stopped and saved during the maintenance time. Affected:
  *   [https://staging.osparc.io](https://staging.osparc.io/)
  *   [https://https://staging.s4l-lite.io/](https://https://staging.s4l-lite.io//)
  
  and on premises:
  *   [https://osparc-staging.speag.com](https://osparc-staging.speag.com/)
  *   [https://tip-staging.speag.com](https://tip-staging.speag.com/)
  *   [https://s4l-staging.speag.com](https://s4l-staging.speag.com/)
  *   [https://s4l-lite-staging.speag.com](https://s4l-lite-staging.speag.com/)
  
  
  Reason: Scheduled staging-release of STAGING_NAME_AND_VERSION.
  
  Thanks for your understanding and sorry for the inconveniences,
  
  Your friendly oSparc Team
  
  

Releasing

• Release (release draft)
• Check Release CI
• Check hanging sidecars. Helper command to run in director-v2 CLI simcore-service-director-v2 close-and-save-service <uuid>
• Check deployed
  • aws deploy
  • dalco deploy
• Delete announcement
• Check e2e runs
• Announce

https://github.com/ITISFoundation/osparc-simcore/releases/tag/staging_<sprint_name><version>