Skip to content

🚀 Release v1.83.0 #7682

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
1 of 41 tasks
YuryHrytsuk opened this issue May 15, 2025 · 9 comments
Open
1 of 41 tasks

🚀 Release v1.83.0 #7682

YuryHrytsuk opened this issue May 15, 2025 · 9 comments
Assignees
@giancarloromeo @GitHK @mrnicegyu11 @pcrespov @odeimaiz @mguidon @sanderegg @YuryHrytsuk @matusdrobuliak66 @bisgaard-itis
Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work
Milestone
Bazinga!

Comments

@YuryHrytsuk
Copy link
Contributor

YuryHrytsuk commented May 15, 2025 •
edited by matusdrobuliak66
Loading

Release version

1.83.0

Commit SHA

360fa2e

Previous pre-release

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

Planned date

10 June, 2025

Did the commit CI suceeded?

  • The commit CI succeeded.

Motivation

  • Regular sprint release

Changes

Before release

Devops check 👷

Tests assessment: e2e testing check 🧪

No response

Test assessment: targeted-testing 🔍️

No response

Test assessment: user-testing 🧐

No response

Summary 📝

  • Prepare release link
make release-prod version=<M.m.0>  git_sha=<commit_sha>
  • Draft release changelog
  • Announce maintenance ( ** ANNOUNCE AT LEAST 24 HOURS BEFORE ** )
  • redis add an entry in db scheduled_maintenance with key maintenance {"start": "2023-03-06T13:00:00.000Z", "end": "2023-03-06T15:00:00.000Z", "reason": "Release <vX.X.0>"}. Note the time is in UTC, please adjust accordingly
    • sim4life.io
    • osparc.speag.com
    • osparc.io
    • tip.science
  • status page (https://manage.statuspage.io/)
    • sim4life.io
    • s4l-lite.io
    • osparc.io
    • tip.science
  • mattermost channels
    • maintenance
    • power users
  • Publish draft draft
  • Check release CI

Releasing 🚀

:tada: https://github.com/ITISFoundation/osparc-simcore/releases/tag/v<M.m.0>
@YuryHrytsuk YuryHrytsuk added t:maintenance Some planned maintenance work release Preparation for pre-release/release labels May 15, 2025
@YuryHrytsuk YuryHrytsuk added this to the Bazinga! milestone May 15, 2025
@matusdrobuliak66
Copy link
Collaborator

⚠️⚠️ Run DB script @matusdrobuliak66

After this commit #7677 is deployed, we should do this: https://github.com/ITISFoundation/private-issues/issues/85#issuecomment-2886608706

@GitHK
Copy link
Contributor

GitHK commented May 19, 2025 •
edited
Loading

⚠️⚠️ Validate jupyterfenics:2.0.0 @GitHK

  • only to be done on osparc.io (osparc product)
  • add shared with everybody (group 1, copy from user 19)
  • check that hackme project works as expected
  • if above is OK, add service_compatibility entries to use version 2.0.0 instead of any other previous versions

@matusdrobuliak66
Copy link
Collaborator

matusdrobuliak66 commented May 28, 2025 •
edited
Loading

⚠️⚠️ Check storage celery workers whether they rollout properly

@GitHK
Copy link
Contributor

GitHK commented May 28, 2025 •
edited
Loading

⚠️⚠️ Validate jupyterfenics:2.0.0 @GitHK

  • only take cation for for DALCO PROD

Remove deprecation from the following services:

  • simcore/services/dynamic/jupyter-ml-pytorch:2.2.0
  • simcore/services/dynamic/jupyter-ml-tensorflow:2.2.0
  • simcore/services/comp/osparc-python-runner-tensorflow:1.1.0
  • simcore/services/comp/osparc-python-runner-pytorch:1.1.0

@matusdrobuliak66
Copy link
Collaborator

matusdrobuliak66 commented May 30, 2025 •
edited
Loading

⚠️⚠️ Setup database timeout @matusdrobuliak66 @YuryHrytsuk

SHOW statement_timeout;
SET statement_timeout = '120s';
  • after setup, database needs to be restarted

@mrnicegyu11
Copy link
Member

⚠️⚠️ Setup database timeout @matusdrobuliak66 @YuryHrytsuk

SHOW statement_timeout;
SET statement_timeout = '120s';

* after setup, database needs to be restarted

I guess you found out what caused the postgres-db issues on master on friday with @bisgaard-itis? Thanks a lot! Would it make sense that I make a PR to add this to the alembic migrations, so that all DBs have this settings set always, even local development?

@bisgaard-itis
Copy link
Contributor

⚠️⚠️ Setup database timeout @matusdrobuliak66 @YuryHrytsuk

SHOW statement_timeout;
SET statement_timeout = '120s';

* after setup, database needs to be restarted

I guess you found out what caused the postgres-db issues on master on friday with @bisgaard-itis? Thanks a lot! Would it make sense that I make a PR to add this to the alembic migrations, so that all DBs have this settings set always, even local development?

IMO it makes sense to have this always set. It might be nice to test that the exception raised makes it clear that it was the db which "cancelled" the processing of the query. Because otherwise this could be kind of misleading to developers.

@matusdrobuliak66
Copy link
Collaborator

matusdrobuliak66 commented Jun 2, 2025 •
edited
Loading

⚠️⚠️ modify service_access_rights @matusdrobuliak66 @odeimaiz

sim4life:
Image

  • /iterator-consumer/probe/file needs to be added

osparc.io (+ all deplyments)
substitute 1 --> product group

@bisgaard-itis
Copy link
Contributor

bisgaard-itis commented Jun 4, 2025 •
edited
Loading

Further things which will need to be done for the release, depending/related on the metamodeling:

  • Publish Jsonifier service on sim4life.io. From the sim4life product on aws staging we saw that it is required to add a row in the service_acccess_rights table in the db to ensure the service is available on the S4L product. Moreover, it requires a pricing plan to run on sim4life.
  • Publish osparc client (https://github.com/ITISFoundation/osparc-simcore-clients)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@giancarloromeo giancarloromeo

@GitHK GitHK

@mrnicegyu11 mrnicegyu11

@pcrespov pcrespov

@odeimaiz odeimaiz

@mguidon mguidon

@sanderegg sanderegg

@YuryHrytsuk YuryHrytsuk

@matusdrobuliak66 matusdrobuliak66

@bisgaard-itis bisgaard-itis

Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work
Projects
None yet
Milestone
Bazinga!
Development

No branches or pull requests
10 participants
@giancarloromeo @GitHK @mrnicegyu11 @pcrespov @odeimaiz @mguidon @sanderegg @YuryHrytsuk @matusdrobuliak66 @bisgaard-itis