Skip to content

Commit b4d4217

Browse files
Merge pull request #1471 from run-ai/Update-hotfixes-May7
Update hotfixes-2-20.md
1 parent a04b0dc commit b4d4217

File tree

2 files changed

+16
-1
lines changed

2 files changed

+16
-1
lines changed

docs/home/changelog/hotfixes-2-19.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,15 @@ The following is a list of the known and fixed issues for Run:ai V2.19.
1010

1111
| Internal ID | Hotfix # | Description |
1212
| :---- | :---- | :---- |
13-
| RUN-27636 | 2.19.103 | Fixed a security vulnerability in golang.org.x.crypto related to CVE-2025-22869 with severity HIGH. |
13+
| RUN-27944 | 2.19.111 | Fixed a security vulnerability in `github.com.golang-jwt.jwt.v4` related to CVE-2025-30204 with severity HIGH. |
14+
| RUN-26994 | 2.19.111 | Fixed an issue where session timeouts occurred when using the CLI. |
15+
| RUN-28097 | 2.19.111 | Fixed an issue where the `allocated_gpu_count_per_gpu` metric displayed incorrect data for fractional pods. |
16+
| RUN-27837 | 2.19.110 | Fixed an issue where a node pool’s placement strategy stopped functioning correctly after being edited. |
17+
| RUN-27628 | 2.19.109 | Fixed an issue where a node pool could remain stuck in Updating status in certain cases. |
18+
| RUN-27640 | 2.19.109 | Fixed a security vulnerability in `github.com.golang-jwt.jwt.v5` related to CVE-2025-30204 with severity HIGH. |
19+
| RUN-27893 | 2.19.109 | Fixed an issue where workloads submitted with an invalid node port range would get stuck in Creating status. |
20+
| RUN-27309 | 2.19.105 | Fixed an issue where workloads configured with a multi node pool setup could fail to schedule on a specific node pool in the future after an initial scheduling failure, even if sufficient resources later became available. |
21+
| RUN-27636 | 2.19.103 | Fixed a security vulnerability in `golang.org.x.crypto` related to CVE-2025-22869 with severity HIGH. |
1422
| RUN-24627 | 2.19.101 | Fixed an issue where GPU_ALLOCATION metric in workloads returned an empty value. |
1523
| RUN-27247 | 2.19.100 | Fixed security vulnerabilities in Spring framework used by `db-mechanic service` - CVE-2021-27568, CVE-2021-44228, CVE-2022-22965, CVE-2023-20873, CVE-2024-22243, CVE-2024-22259 and CVE-2024-22262. |
1624
| RUN-26359 | 2.19.99 | Fixed an issue in CLI v2 where using the `--toleration` option required incorrect mandatory fields. |

docs/home/changelog/hotfixes-2-20.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,13 @@ This section provides details on all hotfixes available for version 2.20. Hotfix
1111

1212
| Version | Date | Internal ID | Description |
1313
|--|--|--|--|
14+
| 2.20.41 | 06/05/2025 | RUN-28241 | Fixed a security vulnerability in `github.com.golang-jwt.jwt.v5` related to CVE-2025-30204 with severity HIGH. |
15+
| 2.20.41 | 06/05/2025 | RUN-28097 | Fixed an issue where the `allocated_gpu_count_per_gpu metric` displayed incorrect data for fractional pods. |
16+
| 2.20.41 | 06/05/2025 | RUN-28006 | Fixed an issue where tokens became invalid for the API server after one hour. |
17+
| 2.20.41 | 06/05/2025 | RUN-27638 | Fixed a security vulnerability in axios related to CVE-2025-27152 with severity HIGH. |
18+
| 2.20.40 | 30/04/2025 | RUN-27837 | Fixed an issue where a node pool’s placement strategy stopped functioning correctly after being edited.|
19+
| 2.20.40 | 30/04/2025 | RUN-27628 | Fixed an issue where a node pool could remain stuck in Updating status in certain cases. |
20+
| 2.20.40 | 30/04/2025 | RUN-27893 | Fixed an issue where workloads submitted with an invalid node port range would get stuck in Creating status. |
1421
| 2.20.39 | 24/04/2025 | RUN-26359 | Fixed an issue in CLI v2 where using the `--toleration` option required incorrect mandatory fields. |
1522
| 2.20.39 | 24/04/2025 | RUN-27088 | Fixed a security vulnerability in tar-fs related to CVE-2024-12905 with severity HIGH. |
1623
| 2.20.39 | 24/04/2025 | RUN-26608 | Fixed an issue by adding a flag to the `cli config set` command and the CLI install script, allowing users to set a cache directory. |

0 commit comments

Comments
 (0)