Skip to content

Commit 1418e48

Browse files
chore: update CHANGELOG.md for v2.1.28
1 parent 39d5323 commit 1418e48

1 file changed

Lines changed: 28 additions & 0 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,31 @@
1+
## v2.1.28 - 2026-10-03
2+
## Version 2.1.28
3+
4+
### New Features
5+
- **Reports API**:
6+
- Added support for retrieving the character encoding of downloaded report documents. The encoding is available as `response.character_code`. If a character code is explicitly provided, it is echoed back; otherwise, it is resolved from the document response's `Content-Type`. For metadata-only calls, `response.character_code` is `None`.
7+
8+
### Bug Fixes
9+
- **Reports API**:
10+
- Fixed an issue where the character encoding information could be incorrectly set or omitted when handling report documents.
11+
12+
### Internal
13+
- **Dependencies**:
14+
- Updated `pytz` dependency to version 2026.4 in both `requirements.txt` and `docs/requirements.txt`.
15+
- Updated `boto3` dependency to version 1.43.105 in both `requirements.txt` and `docs/requirements.txt`.
16+
17+
### Diagram of Character Encoding Handling
18+
```mermaid
19+
graph TD;
20+
A[Request Report Document] --> B{Download/Decrypt};
21+
B -->|Yes| C[Resolve Character Encoding];
22+
B -->|No| D[Set character_code to None];
23+
C --> E[Return ApiResponse with character_code];
24+
D --> E;
25+
```
26+
27+
These changes enhance the usability of the Reports API by providing more detailed information about document encoding, which is crucial for correctly processing and displaying report data.
28+
129
## v2.1.27 - 2026-10-03
230
## Version 2.1.27
331

0 commit comments

Comments
 (0)