This is a security patch release only. No functionality has been added or changed in this release.
-
This release provides container security patches.
-
Elasticsearch is upgraded to version 7.16.2.
-
When directory names are empty (“”) or contain the slash (/) character, execution failures and a dispatcher crash occur.
-
When upgrading from Domino 4.x to 5.1, Domino does not correctly handle environment revisions that have both a Docker image and a base environment revision. This issue is resolved in Domino 5.2.0.
Note
-
Sync operations for deployments backed by SMB file stores can sometimes result in unintended file deletions. This issue is fixed in Domino 5.2.0.
-
You cannot delete a
.gitignore
file in a Domino File System (DFS)-based project. This issue is fixed in Domino 5.2.0.
-
Apps may fail with unusual error messages. This issue is resolved in Domino 5.2.0.
-
Opening an un-cached workspace can cause the workspace to get stuck in the "Pulling" status. This is fixed in Domino 4.6.4.
-
When an API key explicitly passed as an
api_key
argument and theDOMINO_TOKEN_FILE
environment variable is set, Domino uses the token authentication. This issue is resolved in Domino 5.2.0.
-
When Flask apps generate links, this can result in unwanted
302 redirect
behavior. This issue is fixed in Domino 5.2.0.
-
When a Model API fails while retrieving files from git using SSH keys, the private key and the key password, if any, may be exposed in the Domino log. This issue is resolved in Domino 5.2.0.
-
The Import Project drop-down does not display projects owned by organizations of which you are a member. This issue is resolved in Domino 5.2.0.
-
When starting a workspace, the application sometimes gets stuck in the Pulling status, even though the logs indicate that the workspace started successfully. If this occurs, stop and start the workspace again. This issue is fixed in Domino 5.2.0.