🚑️ Release hotfix/v1.79.3 (hotfix)

[pcrespov]

Release version

1.79.3

Branching Commit SHA

61eb77b Tagged as hotfix_v1_79_x, v1.79.2

Previous release

https://github.com/ITISFoundation/osparc-simcore/releases/tag/v1.79.2

Planned date

Undefined

Motivation

• Fixes db overload 🐛 Add project name search parameter for project listing for the API server usecase 🚨 #7066
• Fixes autoscaling too greedy replacing hot buffers 🐛Autoscaling: Fix issue where all warm buffers would be used to replace hot buffers (🚨) #7079
• Update ci-testing-deploy.yml -> To ignore failing webserver integration test

Cherry Picks

• 🐛 Add project name search parameter for project listing for the API server usecase 🚨 #7066
• 🐛Autoscaling: Fix issue where all warm buffers would be used to replace hot buffers (🚨) #7079

🚑️ Hotfix branch

• create hotfix branch hotfix_v1_51_x directly in upstream repo.
  • WARNING: never push this branch BEFORE the actual release is completed
  • Do not delete hotfix branches at least until next full release takes place.
  • See more details
• prepare hotfix by applying patches/cherry-picks (see what changed section)
• test hotfix in local deployment
• push and check whether CI passed
• check images in dockerhub

Hotfix Commit SHA

No response

Changes (for changelog)

No response

Releasing 🚀

• make release-hotfix version=<version> git_sha=<hotfix_commit_sha>
• Draft release notes 🚀
• No need for maintenance announcement?: Target update of <target_service>
• Deploy hot-fix.
  • release 🚀 !!!!
  • aws-prod (updated target service)
  • dalco-prod (updated target service)
  • ti (updated target service)
• Test and Monitor. Revert back if needed!
• Update Release notes (https://github.com/ITISFoundation/osparc-issues/blob/master/scripts/run_after_hotfix_to_prod.py)
• Announce hot-fix

:tada: https://github.com/ITISFoundation/osparc-simcore/releases/tag/v<version>

[pcrespov]

@matusdrobuliak66 I am a bit confused about how you are doing the releases and hotfixes

AFAIK, the release tags (to production) should be next to a staging tag since we always release to production after staging. I would have expected also that the hotfix branch upstream/hotfix_v1_79_x to be starting from v1.79.0 instead of staging_evenHorizon6

[matusdrobuliak66]

@pcrespov I think you need to locally fetch your tags. v1.79.0 = staging_evenHorizon6
https://github.com/ITISFoundation/osparc-simcore/tags

More context: It was tagged at some point, and then additional staging releases were made. Therefore, it was re-tagged.

[matusdrobuliak66]

Manual hotfix info:

#6728 (comment)

[matusdrobuliak66]

done for osparc.io, sim4life and tip.science