Releases: SwissDataScienceCenter/renku
0.54.1
Renku 0.54.1 introduces a few bug fixes in the notebooks and data services components.
User-Facing Changes
🐞 Bug Fixes
- Notebooks: Patch the correct environment variables when a session is resumed after being hibernated
- Data Services: Assign the correct project permissions to group members
Individual components
0.54.0
User-Facing Changes
✨ Improvements
- Test the cloud storage connection before persisting the configuration #3194
- Prompt for cloud storage credentials on v2 session start #3203
- Indicate repository permissions in Renku 2.0 #3136
Internal Changes
🌟 New Features
- Secrets: Allow rotating the private key for secrets storage
Individual Components
0.53.1
Internal Changes
🐞 Bug Fixes
- Search Services: Set keycloak url into the allow list of JWT
issuer urls. This setting is now mandatory to the search-api
service.
Individual Components
0.53.0
User-Facing Changes
🌟 New Features
- Search Services: Enable admin to search without restrictions.
Support fornamespacesearch term in user query.
✨ Improvements
- UI: Convert font-awesome icons to bootstrap icons (#3173, #3161)
- UI: Improve membership maintenance UX in Renku 2.0 (#3154)
- UI: Small updates to the connected services page (#3149)
Internal Changes
🌟 New Features
- Search Services: Adds a
/versionendpoint
🐞 Bug Fixes
- Search Services: Improve verifying JWT tokens using public key from keycloak
- UI: Show project members on the project information page in Renku 2.0 (#3143)
- UI: Fix project page nav in small view ports in Renku 2.0 (#3168, #3169)
- UI: Update session buttons in Renku 2.0 (#3172)
- UI: Update session badges on the project page of Renku 2.0 (#3174, #3175)
- UI: Redirect to group page after creation in Renku 2.0 (#3177)
- UI: Show a full page 404 when a group or project is not accessible in Renku 2.0 (#3162, #3176, #3153)
- UI: Fix updating project keywords in Renku 2.0 (#3187)
- Data services: Fix pagination on the
/namespacesAPI endpoint - Data services: Silence "Preferences not found for user" exceptions and stack traces
Individual Components
0.52.2
Renku 0.52.2 fixes a bug in Data Service.
Internal Changes
🌟 New Features
- Data services: Add endpoint for repository permissions for connected services.
🐞 Bug Fixes
- Data service: Fix typing issue preventing the service from starting when sentry is enabled.
- Data service: Prevent removing all owners from Renku 2.0 resources.
Individual Components
0.52.1
Renku 0.52.1 fixes a few bugs in Renku 2.0, namely cases where:
- sessions could not start if the parent project listed zero repositories and one or more cloud storages to mount
- long running data migrations for user namespaces would cause the data service to keep restarting and never start
This release also includes minor improvements on the backend that will not be visible to users.
Breaking Changes
This release changes the name of the background jobs that synchronize
the data service with Keycloak and also changes the corresponding section for these jobs in the values file.
These jobs have a more general name because they will perform data migrations for the data service in addition to
synchronizing with Keycloak. This requires additional actions from administrators only if you are setting custom
values for dataService.keycloakSync in the values file, but in most cases the default images set in this
section will be used so no action will be required.
User-Facing Changes
🐞 Bug Fixes
- Notebooks: Do not add storage mounts patches when a session has no repository (
#1892 <https://github.com/SwissDataScienceCenter/renku-notebooks/pull/1892>_)
Internal Changes
🌟 New Features
- Data services: Configure trusted reverse proxies
- Data services: Send message queue events in a background process
- Data services: Run asynchronous code in database migrations
- Data services: Support PKCE for authentication with connected services
- Data services: Send group events to the message queue
🐞 Bug Fixes
- Data service: Do not perform data migrations for user namespaces at startup
- Data service: Remove leading underscores on route names
- Data service: Do not crash when a user that is already in a resource pool is added again to the same pool
Individual Components
renku-notebooks 1.25.1 <https://github.com/SwissDataScienceCenter/renku-notebooks/releases/tag/1.25.1>_renku-data-services 0.13.0 <https://github.com/SwissDataScienceCenter/renku-data-services/releases/tag/v0.13.0>_
0.52.0
Renku 0.52.0 introduces a new feature to save and use secrets in RenkuLab sessions. For example, save your credentials for a database or external computing resource in RenkuLab to access those external systems from a RenkuLab session. Save secrets via the new User Secrets page in the account drop down, and choose which secrets to mount in a session on the Start with Options page. More details on this feature can be found in the documentation.
Administrators can customize the culling times (the length of time before an idle session is paused or a paused session is deleted) for different resource pools.
This release also contains new features related to Renku 2.0. However, Renku 2.0 is still in early development and is not yet accessible to users. For more information, see our blog.
User-Facing Changes
🌟 New Features
- Data Services: Add new secrets storage service for managing user session secrets, including new endpoints on data-service to manage these secrets.
- Data Services: Add the possibility for users to connect Renku 2.0 projects to external services, allowing users to clone, pull and push repositories e.g. from GitLab.com or GitHub.com.
- Notebooks: Add support for repositories from external services in Renku 2.0 sessions.
- UI: Add a new User Secrets page to manage secrets, and extend the session launch pages to select secrets to include in the session. (#3101).
- UI: Customize culling times for resource pools (#3113).
- UI: Introduce a new design for Renku 2.0 project pages (#3108).
- UI: Update the user interface to reflect changes to Renku 2.0 sessions (#3122).
- UI: Add support for Renku 2.0 authorization implementation and roles (3.27.0).
✨ Improvements
- Search Services: Add support for groups, namespaces and project keywords.
- UI: Introduce formal navigation for Renku 2.0 pages (#3095).
- UI: Use namespace/slug to identify Renku 2.0 projects (#3103).
Internal Changes
New Features
- Data Services: Update the authorization for access to Renku 2.0 projects and groups to work with Authzed DB, a 3rd party database dedicated to saving authorization data and making authorization decisions
- Search Services: Support processing v2 schema messages (alongside with v1). Make the query parser more lenient to not raise parsing errors.
Bug Fixes
- Data Services: Allow removing tolerations and affinities on resource pools via PATCH requests
Individual Components
0.51.1
Renku 0.51.1 fixes a bug where sessions were not considering the case (upper or lower) of the project name that was being cloned when a session is started. This resulted in the working directory being set to one location and the project cloned in another. This bug only affected projects where users have manually changed their project paths to include uppercase characters or for projects that were not created through Renku but were imported after creation.
User-Facing Changes
🐞 Bug Fixes
- Notebooks: Use the case sensitive project name when cloning repositories at startup
Individual Components
0.51.0
Renku 0.51.0 introduces new features related to Renku 2.0. However, Renku 2.0 is still in early development and is not yet accessible to users. For more information, see our [roadmap](https://github.com/SwissDataScienceCenter/renku-design-docs/blob/main/roadmap.md).
- This release introduces groups to Renku 2.0.
- Various bug fixes and improvements
User-Facing Changes
🌟 New Features
- UI: A new entity, groups, has been introduced to Renku 2.0. Groups are a way to organize projects in Renku 2.0.
- UI: Projects are always in a group -- either the user's implicitly-created group, or a group that has been explicitly created.
✨ Improvements
- UI Add an "email us" button below the session class selector to request more resources (#3073)
🐞 Bug Fixes
- Data service: Allow proper removal of users from resource pools
- Data service: Enable searching for all users when adding users to resource pools
Internal Changes
🌟 New Features
-
Data services: Initial support for groups
🐞 Bug Fixes
-
Data service: Increase timeout for synchronizing Keycloak users
Individual Components
0.50.0
Renku 0.50.0 introduces several new features related to Renku 2.0:
- This release introduces new sew search functionality for Renku 2.0.
- Support has been added for interactive sessions in Renku 2.0 projects.
However, Renku 2.0 is still in early development and is not yet accessible to users. For more information, see our Renku 2.0 blog post and check out our roadmap.
User-Facing Changes
🌟 New Features
- UI: Renku 2.0 Search page with initial support for project and user search (alpha release)
- UI: Support for interactive sessions in Renku 2.0 projects, comprising global session environments and session launchers (alpha release)
- Notebooks: Initial support for Renku 2.0 sessions, supporting mounting multiple repositories (alpha release)
- UI: Add a new navigation top bar for Renku 2.0 (alpha release)
- UI: Add an ad-hoc feature flag for Renku 2.0 (alpha release)
✨ Improvements
- UI Update the footer links section with Mastodon (#3081, #3059)
- UI Improve session scheduling error messages (#3082, #3036)
🐞 Bug Fixes
Internal Changes
New Features
- Data services: Initial support for project and user search for Renku 2.0 (alpha release)
- Data services: Add support for sentry and prometheus
- Data services: Initial support for Renku 2.0 session environments and session launchers (alpha release)
- Search services: Initial support for project and user search for Renku 2.0 (alpha release)
Improvements
- KG: Jena 5.0.0 upgrade