fix: revert amalthea upgrade from 0.20.0 to 0.19.2#4085
Merged
Conversation
olevski
force-pushed
the
revert-amalthea-upgrade
branch
from
4842b45 to
e09ebdf
Compare
olevski
changed the title
Collaborator
|
You can access the deployment of this PR at https://ci-renku-4085.dev.renku.ch |
aledegano
approved these changes
Jul 4, 2025
Collaborator
|
Tearing down the temporary RenkuLab deployment for this PR. |
rokroskar
pushed a commit
that referenced
this pull request
Jul 8, 2025
Reverts a feature merged in release #4072
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This was causing all Amlthea CRDs to be deleted - if they were installed with the helm chart. The tests did not catch this because for CI deployments we do not install the CRDs and this part of the code never played out until we deployed to dev.renku.ch.
After this is merged I will remove and then retag Renku release 2.3.0.
NOTE: The target branch is master on purpose.
/deploy