Skip to content
This repository was archived by the owner on Oct 10, 2025. It is now read-only.

Commit c2868ed

Browse files
committed
updates for v1.1.7
1 parent 3b865d4 commit c2868ed

File tree

81 files changed

+11332
-8632
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

81 files changed

+11332
-8632
lines changed

.gitignore

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,4 +51,7 @@ source/infrastructure/test/mock-lambda-func/java-lambda/checkstyle-result.xml
5151
*.log
5252
.venv/**
5353
source/ui/public/pdf.worker.min.mjs
54-
.viperlightrc
54+
.viperlightrc
55+
56+
.temp_redpencil
57+
bom.json

CHANGELOG.md

Lines changed: 24 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
=======
99

10+
## [1.1.7] - 2024-11-18
11+
12+
### Security
13+
14+
- Updated node and python packages to patch vulnerabilities
15+
16+
### Fixed
17+
18+
- Search failure when deployed with exclusively with Amazon OpenSearch option
19+
20+
## [1.1.6] - 2024-10-31
21+
22+
### Security
23+
24+
- Updated node modules to patch vulnerabilities
25+
1026
## [1.1.5] - 2024-09-24
1127

1228
### Security
@@ -39,7 +55,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
3955

4056
## [1.1.0] - 2024-07-03
4157

42-
### Updated
58+
### Changed
4359

4460
- Added OpenSearch support
4561
- Backend bulk documents upload
@@ -69,7 +85,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
6985

7086
## [1.0.9] - 2024-05-16
7187

72-
### Update
88+
### Changed
7389

7490
- Updated java runtime libraries to patch vulnerabilities
7591

@@ -95,27 +111,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
95111

96112
- Fixed a bug in the entity detection code which caused failures on an edge case with repeating words ([issue 34](https://github.com/aws-solutions/enhanced-document-understanding-on-aws/issues/34))
97113

98-
### Updated
114+
### Changed
99115

100116
- Failure on a single entity now does not cause the whole workflow to fail, instead logging an error message and continuing
101117

102118
## [1.0.5] - 2024-03-05
103119

104-
### Updated
120+
### Changed
105121

106122
- Library upgrades to address security vulnerability related to `node-ip` [CVE-2023-42282](https://github.com/advisories/GHSA-78xj-cgh5-2h22)
107123
- Add dependency between Amazon S3 bucket creation and S3 bucket policy to reduce failures with `Fn::GetAtt` when retrieving bucket arn to create bucket policy
108124

109125
## [1.0.4] - 2024-01-11
110126

111-
### Updated
127+
### Changed
112128

113129
- AWS CDK and SDK upgrades
114130
- Fix an intermittent issue in AWS CloudFormation by setting explicit dependencies between resources
115131

116132
## [1.0.3] - 2023-12-07
117133

118-
### Updated
134+
### Changed
119135

120136
- Library upgrades to address security vulnerabilities.
121137
- Fix an issue with sample workflow configurations where `textract` workflow was missing before any `entity` based detection workflow.
@@ -124,14 +140,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
124140

125141
## [1.0.2] - 2023-11-09
126142

127-
### Updated
143+
### Changed
128144

129145
- AWS CDK and SDK version updates
130146
- Library upgrades to address security vulnerabilities.
131147

132148
## [1.0.1] - 2023-10-18
133149

134-
### Updated
150+
### Changed
135151

136152
- Library upgrades to address security vulnerabilities
137153

CODE_OF_CONDUCT.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
## Code of Conduct
22
This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
33
For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
4-
[email protected] with any additional questions or comments.
5-
4+
[email protected] with any additional questions or comments.

0 commit comments

Comments
 (0)