: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>
What kind of pre-release?
master branch
Sprint Name
staging_EventHorizon
Pre-release version
1
Commit SHA
2af7f218f196141a18fef4bf6ef75f0248bd7857Planned date
11.11.2024
Did the commit CI suceeded?
Motivation
...
What Changed
Devops check ⚠️ devops
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>maintenancein every concerned deployment)[ ] Announce release in Mattermost
Releasing
simcore-service-director-v2 close-and-save-service <uuid>