Skip to content

Releases: swan-cern/jupyter-images

swan-cern/v0.0.12

07 Jun 09:15
Compare
Choose a tag to compare
swan-cern: Bump version of swan image to v0.0.8

swan-cern/v0.0.11

29 May 11:55
Compare
Choose a tag to compare
swan-cern: Bump version of SparkConnector to v3.0.4

swan-cern/v0.0.10

29 May 08:55
Compare
Choose a tag to compare
swan-cern: Force Alma9 Spark users to use the old UI by default

This change was introduced temporarily, before fully moving to
JupyterLab and forcing all SWAN users using Alma9 to move to it as well.

When the time is right, i.e., the change to JupyterLab will take place
and this commit can be reverted.

swan/v0.0.7

27 May 14:39
Compare
Choose a tag to compare
swan: Bump version of base image to v0.0.3

swan-cern/v0.0.9

27 May 14:50
Compare
Choose a tag to compare
swan-cern: Bump version of swan image to v0.0.7

base/v0.0.3

27 May 14:23
Compare
Choose a tag to compare
ci: Update kaniko image

swan-cern/v0.0.8

24 May 14:18
Compare
Choose a tag to compare
swan-cern: Enable sparkmonitor extension when a spark cluster is sele…

swan-cern/v0.0.7

24 May 08:25
Compare
Choose a tag to compare
swan-cern: Bump swan image version to v0.0.6

swan/v0.0.6

23 May 13:25
Compare
Choose a tag to compare
swan: Bump base image version to v0.0.2

base/v0.0.2: base: Remove dnf upgrade instruction

23 May 12:46
Compare
Choose a tag to compare
The instruction was removed as we are using a fixed version of the alma9
image, so that the layers on top are based on a stable build. By running
the dnf upgrade instruction we were doing the same thing as if we were
always using the latest version of the alma9-base image, thus having no
stability.