🚀 Pre-release master -> staging_Engage7

[YuryHrytsuk]

What kind of pre-release?

master branch

Sprint Name

Engage

Pre-release version

7

Commit SHA

TBD

Planned date

Thu, 17th July 2025

Did the commit CI suceeded?

• The commit CI succeeded.

Motivation

• Weekly staging release

What Changed

OPS

- Document metabase optional configuration (email, ...) (#1136)
- metabase: add missing env to template (#1135)
- Revert "update grok pattern (#1129)" (#1133)
- Restrict metabase user to tables (#1132)
- Fix portainer makefile (#1131)
- Add portainer registry configuration 🚨 (#1125)
- update grok pattern (#1129)
- Update makefile venv targets (#1126)
- registry mirror: stop-first while updating (#1123)
- Fix monitoring_tempo bug: local_blocks processor traces_storage
- Kubernetes logging: storage configuration (#1110)
- inhouse tip prometheus: scrape simcore services (#1109)
- remove deprecated traefik labels (#1107)
- Fix deploy_ops CD failure - monitoring - 2nd attempt
- Revert "Fix deploy_ops CD step - monitoring"
- Fix deploy_ops CD step - monitoring
- Kubernetes: add local storage (#1100)

Devops check ⚠️ devops

• Add portainer registry configuration 🚨 osparc-ops-environments#1125

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 and deployed