🚀 Pre-release master -> staging_Singularity2

[YuryHrytsuk]

What kind of pre-release?

master branch

Sprint Name

Singularity

Pre-release version

2

Commit SHA

a8a8046f2124f685a8d5914e17a49413b53a4934

Planned date

Feb 6th, 2025

Did the commit CI suceeded?

• The commit CI succeeded.

Motivation

• Weekly staging release

What Changed

• ✨ Updates licensed_items table 🗃️ #7144 by @pcrespov
• 🎨 Changing Rest Model for licensed items listing (🗃️) #7139 by @matusdrobuliak66
• 🎨 Minor: ooil prints warning when one subfolder (of potentially many) doesn't contain metadata.yml #7128 by @mrnicegyu11
• Add licensing endpoints to api check and improve backwards compatibility checks #7157 by @bisgaard-itis
• 🎨 [Frontend] Standalone (full screen) UI mode #7138 by @odeimaiz
• 🎨 [Frontend] Licensed items: Adapt to new model and backend's catalog #7146 by @odeimaiz
• 🎨 [Frontend] Feature: Study icon #7155 by @odeimaiz
• ♻️ Adding lifespan support for FastAPI & migrated dynamic-scheduler to use it #7149 by @GitHK
• 🐛 Removed tracing lifespan which should be an initialize #7165 by @GitHK
• 🎨 [Frontend] UI/UX Data handling: Larger window and list view by default #7160 by @odeimaiz
• ✨ Sync task that auto-registers items from VIP as licensed items in the system ⚠️ 🗃️ 🚨  #7140 by @pcrespov
• 🎨 [Frontend] Enh: Merge Preferences into My Account #7173 by @odeimaiz
• 🎨 [Frontend] Enh: Tags UX #7169 by @odeimaiz
• 🐛 fixes failure due to nullable doi in licensed-items web-api response #7177 by @pcrespov
• ♻️ [Frontend] ViP Market: adapt to latest model #7164 by @odeimaiz

Devops check ⚠️ devops

• Remove filestash label
• [NIH STAG] Remove postgrs label
  • Remove volume if exists
• Remove prometheuscadviosr label

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>

[YuryHrytsuk]

Done