Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions requirements-test.txt
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,9 @@ blinker==1.9.0 \
# via
# -r requirements.txt
# flask
boto3==1.42.96 \
--hash=sha256:2f4566da2c209a98bdbfc874d813ef231c84ad24e4f815e9bc91de5f63351a24 \
--hash=sha256:b38a9e4a3fbbee9017252576f1379780d0a5814768676c08df2f539d31fcdd68
boto3==1.43.41 \
--hash=sha256:0f56811f13677bfb4542daa0cce8532c95d9afd27b4ba7b681af36a0568624ad \
--hash=sha256:f48f862d2720ea9203ed2d842d436b8eb2d459ea31654a7ad7c0756fdf36c6b2
# via -r requirements.txt
botocore==1.42.96 \

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

Same botocore==1.42.96 mismatch in the test requirements file. boto3 1.43.25 requires botocore>=1.43.25, so test environment installation will also fail.

Suggested fix: Bump botocore to the version required by boto3 1.43.25 in requirements-test.txt, updating hashes accordingly.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

Same botocore version mismatch as in requirements.txt. botocore==1.42.96 is incompatible with boto3==1.43.27. Test environment installation will fail.

Suggested fix: Update botocore to match the version required by boto3 1.43.27 in requirements-test.txt.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

Same issue in the test requirements: boto3 is updated to 1.43.28 but botocore remains at 1.42.96. pip install with hash checking will fail because boto3 1.43.28 requires botocore>=1.43.28.

Suggested fix: Update botocore to 1.43.28 (with correct hashes) in requirements-test.txt.

--hash=sha256:75b3b841ffacaa944f645196655a21ca777591dd8911e732bfb6614545af0250 \
Expand Down
6 changes: 3 additions & 3 deletions requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,9 @@ blinker==1.9.0 \
--hash=sha256:b4ce2265a7abece45e7cc896e98dbebe6cead56bcf805a3d23136d145f5445bf \
--hash=sha256:ba0efaa9080b619ff2f3459d1d500c57bddea4a6b424b60a91141db6fd2f08bc
# via flask
boto3==1.42.96 \
--hash=sha256:2f4566da2c209a98bdbfc874d813ef231c84ad24e4f815e9bc91de5f63351a24 \
--hash=sha256:b38a9e4a3fbbee9017252576f1379780d0a5814768676c08df2f539d31fcdd68
boto3==1.43.41 \
--hash=sha256:0f56811f13677bfb4542daa0cce8532c95d9afd27b4ba7b681af36a0568624ad \
--hash=sha256:f48f862d2720ea9203ed2d842d436b8eb2d459ea31654a7ad7c0756fdf36c6b2
# via iib (setup.py)
botocore==1.42.96 \

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is updated to 1.43.25 but botocore remains pinned at 1.42.96. boto3 1.43.25 requires botocore>=1.43.25,<1.44.0. This version mismatch will cause pip to fail dependency resolution at install time, breaking all builds. The same mismatch exists in requirements-test.txt at line 35.

Suggested fix: Update botocore to 1.43.25 (with correct hashes) in both requirements.txt and requirements-test.txt. Also verify s3transfer 0.16.1 is compatible with boto3 1.43.25; if not, update it as well.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is bumped to 1.43.25 but botocore remains pinned at 1.42.96. boto3 strictly requires a matching botocore version (botocore>=1.43.25,<1.44.0). This will cause pip install to fail with a dependency conflict, making the application uninstallable.

Suggested fix: Bump botocore to 1.43.25 (or the exact version required by boto3 1.43.25) in both requirements.txt and requirements-test.txt, updating the hashes accordingly. Also verify that s3transfer==0.16.1 is compatible with boto3 1.43.25; if not, bump it as well.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is updated to 1.43.27 but botocore remains pinned at 1.42.96. boto3 and botocore minor versions are always locked in step: boto3 1.43.27 requires botocore>=1.43.27,<1.44.0. botocore 1.42.96 does not satisfy this constraint, so pip installation will fail with a dependency resolution error.

Suggested fix: Update botocore to 1.43.27 (or the exact version required by boto3 1.43.27) in requirements.txt. Also verify s3transfer==0.16.1 compatibility and update if needed. Ideally regenerate the lockfile with pip-compile.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is updated to 1.43.28 but botocore remains pinned at 1.42.96. boto3 declares a strict dependency on a matching botocore version (botocore>=1.43.28,<1.44.0 for boto3 1.43.28). This version mismatch will cause pip to fail dependency resolution, making the application uninstallable.

Suggested fix: Update botocore to the version required by boto3 1.43.28 (i.e., botocore==1.43.28) in both requirements.txt and requirements-test.txt. Also verify s3transfer compatibility.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is bumped to 1.43.29 but botocore remains pinned at 1.42.96 in both requirements.txt and requirements-test.txt. boto3 has a strict dependency on a matching botocore version (botocore>=1.43.29,<1.44.0 for boto3 1.43.29). botocore 1.42.96 does not satisfy this constraint, so pip install with these requirements will fail on dependency resolution.

Suggested fix: Update botocore to 1.43.29 (or the exact version required by boto3 1.43.29) in both requirements.txt and requirements-test.txt, including updated hashes. Re-run pip-compile or the equivalent tooling to regenerate a consistent lockfile. Also verify s3transfer==0.16.1 compatibility with the new boto3/botocore pair.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is bumped to 1.43.30 but botocore remains pinned at 1.42.96 (requirements.txt line 27, requirements-test.txt line 35). boto3 strictly requires a matching botocore version (boto3 1.43.x requires botocore>=1.43.30,<1.44.0). This version mismatch will cause pip to fail to resolve dependencies, resulting in an installation failure. Additionally, s3transfer==0.16.1 (requirements.txt line 1065, requirements-test.txt line 1272) will likely need updating as well since it depends on a compatible botocore range. All three packages (boto3, botocore, s3transfer) must be updated together.

Suggested fix: Bump botocore to 1.43.30 (or the matching version required by boto3 1.43.30) in both requirements.txt and requirements-test.txt. Also update s3transfer to the version compatible with botocore 1.43.x. All three packages must be updated as a set.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is updated to 1.43.31 but botocore remains pinned at 1.42.96. boto3==1.43.31 requires botocore>=1.43.31,<1.44.0 (boto3 and botocore versions are always released in lockstep with matching lower bounds). With botocore pinned at 1.42.96, pip will produce a dependency resolution error and installation will fail. The same mismatch exists in requirements-test.txt (line 35). s3transfer==0.16.1 is likely still compatible with boto3 1.43.x but should be verified.

Suggested fix: Update botocore to at least 1.43.31 in both requirements.txt and requirements-test.txt (including updated hashes). Re-run pip-compile or the equivalent lock-file generation tool to produce a consistent set of pinned dependencies. Verify s3transfer compatibility as well.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is bumped to 1.43.33 but botocore remains pinned at 1.42.96. boto3 strictly requires a matching botocore version (boto3 1.43.x requires botocore>=1.43.33,<1.44.0). This version mismatch will cause pip to fail with a dependency resolution error during installation. The same mismatch exists in requirements-test.txt at line 35. The s3transfer pin at 0.16.1 may also be incompatible, as newer boto3 releases sometimes require updated s3transfer versions.

Suggested fix: Update botocore to the version required by boto3 1.43.33 (botocore==1.43.33) in both requirements.txt and requirements-test.txt. Verify that s3transfer==0.16.1 is compatible with boto3 1.43.33 and update if necessary. Ideally, regenerate both lockfiles with pip-compile to ensure all transitive dependencies are consistent.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] api-contract

boto3 is bumped to 1.43.34 but botocore remains pinned at 1.42.96 in both requirements.txt (line 27) and requirements-test.txt (line 35). boto3 strictly requires a matching botocore version (boto3 1.43.x requires botocore>=1.43.34,<1.44.0). The current botocore==1.42.96 falls outside that range and will cause a dependency resolution failure at install time. s3transfer==0.16.1 may also need updating depending on the exact compatibility window.

Suggested fix: Update botocore (and s3transfer if needed) in both requirements.txt and requirements-test.txt to the versions required by boto3==1.43.34. Run pip-compile or equivalent to regenerate the lock files so all three packages are mutually compatible.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is updated to 1.43.35 but botocore remains pinned at 1.42.96 in both requirements.txt and requirements-test.txt. boto3 declares an exact dependency on its matching botocore version (boto3 1.43.x requires botocore>=1.43.35,<1.44.0). This mismatch will cause pip to fail dependency resolution at install time. s3transfer==0.16.1 may also be incompatible with boto3 1.43.35.

Suggested fix: Update botocore to 1.43.35 (with correct hashes) in both requirements.txt and requirements-test.txt. Verify s3transfer==0.16.1 compatibility with boto3 1.43.35 and update if needed. Alternatively, regenerate the lockfiles with pip-compile to resolve all versions consistently.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[critical] dependency version mismatch

boto3 is updated to 1.43.36 but botocore remains pinned at 1.42.96. boto3 declares a strict dependency on a matching botocore version (boto3==1.43.x requires botocore>=1.43.36,<1.44.0). This version conflict will cause pip to fail during dependency resolution when hash-checking mode is active (as it is here), since the required botocore 1.43.36 is not listed and the pinned 1.42.96 does not satisfy the constraint. The same mismatch exists in requirements-test.txt.

Suggested fix: Update botocore to 1.43.36 (with correct hashes) in both requirements.txt and requirements-test.txt to match the boto3 version.

--hash=sha256:75b3b841ffacaa944f645196655a21ca777591dd8911e732bfb6614545af0250 \
Expand Down
Loading