From e507fcfc533616adfae79d923669ab99ae87894c Mon Sep 17 00:00:00 2001 From: mrjones-plip Date: Wed, 1 Apr 2026 08:03:12 -0700 Subject: [PATCH 1/4] chore(na): 5.1.1 and 5.0.3 release notes --- content/en/releases/5_0_3.md | 39 +++++++++++++++++++++++++++++++++++ content/en/releases/5_1_1.md | 39 +++++++++++++++++++++++++++++++++++ content/en/releases/_index.md | 2 ++ 3 files changed, 80 insertions(+) create mode 100644 content/en/releases/5_0_3.md create mode 100644 content/en/releases/5_1_1.md diff --git a/content/en/releases/5_0_3.md b/content/en/releases/5_0_3.md new file mode 100644 index 000000000..e3fbefa28 --- /dev/null +++ b/content/en/releases/5_0_3.md @@ -0,0 +1,39 @@ + +--- +title: "5.0.3 release notes" +linkTitle: "5.0.3" +sidebar: + exclude: true +description: + Released 2026-04-01 +--- + +## Highlights + +This release fixes a bug when an instance has one or more users with a large amount of documents (>150k). Deployments that suffer from this bug will see their services restart every time the user(s) tries to sync. In the API logs, this will show: + +``` +2026-04-01T06:30:14.828 ERROR: Server error: RangeError: Maximum call stack size exceeded + at getDocsByReplicationKeyNouveau (/service/api/src/services/authorization.js:640:10) + at process.processTicksAndRejections (node:internal/process/task_queues:105:5) + at async Object.getContext (/service/api/src/services/replication.js:10:32) + at async getDocIds (/service/api/src/controllers/replication.js:7:23) { + [stack]: [Getter/Setter], + [message]: 'Maximum call stack size exceeded' +} +``` + +### Bug fixes + +- [#10792](https://github.com/medic/cht-core/issues/10792): Replication get-ids can fail for extremely large users (over 150.000 documents) + +## Known issues + +Check the repository for the [latest known issues](https://github.com/medic/cht-core/issues?q=is%3Aissue+label%3A%22Affects%3A+5.1.1%22). + +## Contributors + +Thanks to all who committed changes for this release! + +* [Diana Barsan](https://github.com/dianabarsan) +* [Elijah Karari](https://github.com/eljhkrr) diff --git a/content/en/releases/5_1_1.md b/content/en/releases/5_1_1.md new file mode 100644 index 000000000..d996d10fa --- /dev/null +++ b/content/en/releases/5_1_1.md @@ -0,0 +1,39 @@ + +--- +title: "5.1.1 release notes" +linkTitle: "5.1.1" +sidebar: + exclude: true +description: + Released 2026-04-01 +--- + +## Highlights + +This release fixes a bug when an instance has one or more users with a large amount of documents (>150k). Deployments that suffer from this bug will see their services restart every time the user(s) tries to sync. In the API logs, this will show: + +``` +2026-04-01T06:30:14.828 ERROR: Server error: RangeError: Maximum call stack size exceeded + at getDocsByReplicationKeyNouveau (/service/api/src/services/authorization.js:640:10) + at process.processTicksAndRejections (node:internal/process/task_queues:105:5) + at async Object.getContext (/service/api/src/services/replication.js:10:32) + at async getDocIds (/service/api/src/controllers/replication.js:7:23) { + [stack]: [Getter/Setter], + [message]: 'Maximum call stack size exceeded' +} +``` + +### Bug fixes + +- [#10792](https://github.com/medic/cht-core/issues/10792): Replication get-ids can fail for extremely large users (over 150.000 documents) + +## Known issues + +Check the repository for the [latest known issues](https://github.com/medic/cht-core/issues?q=is%3Aissue+label%3A%22Affects%3A+5.1.1%22). + +## Contributors + +Thanks to all who committed changes for this release! + +* [Diana Barsan](https://github.com/dianabarsan) +* [Elijah Karari](https://github.com/eljhkrr) diff --git a/content/en/releases/_index.md b/content/en/releases/_index.md index 90714225e..336bf4da6 100644 --- a/content/en/releases/_index.md +++ b/content/en/releases/_index.md @@ -92,7 +92,9 @@ Devices with more navigation systems are more likely to get a more accurate loca ## Release Notes ### 5.x +- [5.1.1](/releases/5_1_1) - 2026-04-01 - [5.1.0](/releases/5_1_0) - 2026-02-26 +- [5.0.3](/releases/5_0_3) - 2026-04-01 - [5.0.2](/releases/5_0_2) - 2026-02-11 - [5.0.1](/releases/5_0_1) - 2025-11-27 - [5.0.0](/releases/5_0_0) - 2025-11-20 From 9a7a78a485da557d649255ca8f104a55d1cb8941 Mon Sep 17 00:00:00 2001 From: mrjones-plip Date: Wed, 1 Apr 2026 09:41:19 -0700 Subject: [PATCH 2/4] remove mentions of restarts per feedback --- content/en/releases/5_0_3.md | 2 +- content/en/releases/5_1_1.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/releases/5_0_3.md b/content/en/releases/5_0_3.md index e3fbefa28..32ff1f3c7 100644 --- a/content/en/releases/5_0_3.md +++ b/content/en/releases/5_0_3.md @@ -10,7 +10,7 @@ description: ## Highlights -This release fixes a bug when an instance has one or more users with a large amount of documents (>150k). Deployments that suffer from this bug will see their services restart every time the user(s) tries to sync. In the API logs, this will show: +This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000). Deployments that suffer from this bug will see an error in the API logs: ``` 2026-04-01T06:30:14.828 ERROR: Server error: RangeError: Maximum call stack size exceeded diff --git a/content/en/releases/5_1_1.md b/content/en/releases/5_1_1.md index d996d10fa..dae824820 100644 --- a/content/en/releases/5_1_1.md +++ b/content/en/releases/5_1_1.md @@ -10,7 +10,7 @@ description: ## Highlights -This release fixes a bug when an instance has one or more users with a large amount of documents (>150k). Deployments that suffer from this bug will see their services restart every time the user(s) tries to sync. In the API logs, this will show: +This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000). Deployments that suffer from this bug will see an error in the API logs: ``` 2026-04-01T06:30:14.828 ERROR: Server error: RangeError: Maximum call stack size exceeded From fe270480e29859cd5387a2213a0bc71a4f4f570b Mon Sep 17 00:00:00 2001 From: mrjones-plip Date: Wed, 1 Apr 2026 13:31:22 -0700 Subject: [PATCH 3/4] tidy up release notes to not have full error per feedback --- content/en/releases/5_0_3.md | 13 +------------ content/en/releases/5_1_1.md | 13 +------------ 2 files changed, 2 insertions(+), 24 deletions(-) diff --git a/content/en/releases/5_0_3.md b/content/en/releases/5_0_3.md index 32ff1f3c7..51630deac 100644 --- a/content/en/releases/5_0_3.md +++ b/content/en/releases/5_0_3.md @@ -10,18 +10,7 @@ description: ## Highlights -This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000). Deployments that suffer from this bug will see an error in the API logs: - -``` -2026-04-01T06:30:14.828 ERROR: Server error: RangeError: Maximum call stack size exceeded - at getDocsByReplicationKeyNouveau (/service/api/src/services/authorization.js:640:10) - at process.processTicksAndRejections (node:internal/process/task_queues:105:5) - at async Object.getContext (/service/api/src/services/replication.js:10:32) - at async getDocIds (/service/api/src/controllers/replication.js:7:23) { - [stack]: [Getter/Setter], - [message]: 'Maximum call stack size exceeded' -} -``` +This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000). Deployments that suffer from this bug will see an error in the API logs (`Maximum call stack size exceeded`). See the ticket below for more details. ### Bug fixes diff --git a/content/en/releases/5_1_1.md b/content/en/releases/5_1_1.md index dae824820..2dd18b855 100644 --- a/content/en/releases/5_1_1.md +++ b/content/en/releases/5_1_1.md @@ -10,18 +10,7 @@ description: ## Highlights -This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000). Deployments that suffer from this bug will see an error in the API logs: - -``` -2026-04-01T06:30:14.828 ERROR: Server error: RangeError: Maximum call stack size exceeded - at getDocsByReplicationKeyNouveau (/service/api/src/services/authorization.js:640:10) - at process.processTicksAndRejections (node:internal/process/task_queues:105:5) - at async Object.getContext (/service/api/src/services/replication.js:10:32) - at async getDocIds (/service/api/src/controllers/replication.js:7:23) { - [stack]: [Getter/Setter], - [message]: 'Maximum call stack size exceeded' -} -``` +This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000). Deployments that suffer from this bug will see an error in the API logs (`Maximum call stack size exceeded`). See the ticket below for more details. ### Bug fixes From 401d6e5e4b00d33e28a8ec4966ee12f3f22f1961 Mon Sep 17 00:00:00 2001 From: mrjones-plip Date: Wed, 1 Apr 2026 13:32:49 -0700 Subject: [PATCH 4/4] moving release date out 1 day --- content/en/releases/5_0_3.md | 2 +- content/en/releases/5_1_1.md | 2 +- content/en/releases/_index.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/releases/5_0_3.md b/content/en/releases/5_0_3.md index 51630deac..c64686e28 100644 --- a/content/en/releases/5_0_3.md +++ b/content/en/releases/5_0_3.md @@ -5,7 +5,7 @@ linkTitle: "5.0.3" sidebar: exclude: true description: - Released 2026-04-01 + Released 2026-04-02 --- ## Highlights diff --git a/content/en/releases/5_1_1.md b/content/en/releases/5_1_1.md index 2dd18b855..fe1144cdb 100644 --- a/content/en/releases/5_1_1.md +++ b/content/en/releases/5_1_1.md @@ -5,7 +5,7 @@ linkTitle: "5.1.1" sidebar: exclude: true description: - Released 2026-04-01 + Released 2026-04-02 --- ## Highlights diff --git a/content/en/releases/_index.md b/content/en/releases/_index.md index 336bf4da6..646fac0ae 100644 --- a/content/en/releases/_index.md +++ b/content/en/releases/_index.md @@ -92,9 +92,9 @@ Devices with more navigation systems are more likely to get a more accurate loca ## Release Notes ### 5.x -- [5.1.1](/releases/5_1_1) - 2026-04-01 +- [5.1.1](/releases/5_1_1) - 2026-04-02 - [5.1.0](/releases/5_1_0) - 2026-02-26 -- [5.0.3](/releases/5_0_3) - 2026-04-01 +- [5.0.3](/releases/5_0_3) - 2026-04-02 - [5.0.2](/releases/5_0_2) - 2026-02-11 - [5.0.1](/releases/5_0_1) - 2025-11-27 - [5.0.0](/releases/5_0_0) - 2025-11-20