Skip to content

Bump Python requirements - #1433

Merged
lipoja merged 1 commit into
release-engineering:mainfrom
lipoja:bump_requirements_2_main
Nov 20, 2026
Merged

lipoja merged 1 commit into
release-engineering:mainfrom
lipoja:bump_requirements_2_main

Conversation

@lipoja

@lipoja lipoja commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Bump Python requirements

Signed-off-by: Jan Lipovský <jlipovsk@redhat.com>
Assisted-by: Codex, Luna 6
@qodo-for-releng

qodo-for-releng Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

PR Summary by Qodo

Refresh pinned Python runtime and test dependencies

⚙️ Configuration changes 🕐 10-20 Minutes

Grey Divider

AI Description

• Bump eight Python packages, including AWS, Kafka, Kubernetes, Pydantic, and SQLAlchemy
 dependencies.
• Refresh package hashes in both lockfiles to keep runtime and test environments aligned.
Merge Risk 🟡 Medium

Blast radius 🔴 High 💥 6 capabilities

  • 6 affected capabilities span independent functional scopes: AWS artifact storage integration, IIB application runtime, IIB relational persistence, IIB request validation and version handling, Kafka event delivery integration, Kubernetes orchestration integration.
  • A failed or incompatible dependency installation/startup prevents the bounded application runtime from serving its existing API and worker behavior.
  • The dependency entries are shared runtime inputs rather than separate end-to-end capabilities.
  • S3 access is a distinct external-storage outcome from messaging, orchestration, persistence, and validation.
  • The changed boto3/botocore pins reach this behavior through the existing storage callers.
  • Publishing an event is an independent external-system outcome from storage, orchestration, persistence, and validation.
  • The confluent-kafka pin directly supplies the existing producer implementation.
  • Kubernetes API operations have a separate cluster-management outcome from the other integrations.
  • The kubernetes, pydantic, and oauthlib upgrades participate in this existing integration path.
  • Relational persistence is an independent end-to-end behavior whose correctness depends on SQLAlchemy and its callers, rather than being an implementation hop of the storage, messaging, or Kubernetes integrations.
  • Validation and semantic-version comparison produce distinct application outcomes from external storage, messaging, orchestration, and persistence.
  • The pydantic, pydantic-core, and semver upgrades reach these existing callers.
Sources

requirements.txt[525-526]

confluent-kafka==2.16.2 \
    --hash=sha256:0373b5d35f6c89e9c38d2caa1e0e0a05ad369b8a2ae08c37820270d8b6181e7f \
Behavioral complexity 🟡 Medium 🧩 Compatibility cases

  • Before, the application used the prior pinned versions and hashes.
  • After, multiple runtime and transitive dependency versions are changed together in both production and test snapshots.
  • The new correctness condition is that the complete resolved environment remains installable and import-compatible across supported deployment and test environments.
  • This is a compatibility condition introduced by the version transition, not a new application algorithm or concurrency protocol.
Potential damage 🟡 Medium 🩹 Temporary loss

  • A startup or installation failure removes application availability until the environment is rebuilt with a compatible dependency set or the dependency pins are reverted.
  • Reverting code alone does not repair an already-built environment; redeployment or environment recreation is required.
  • No persistent application state or external effect is implied by this fault.
  • Recoverable through deployment rollback or environment rebuild, assuming the prior lock snapshot and artifacts remain available; automatic recovery is not established.
Assessed commit 28d26fe
Diagram

graph TD
  A["Package requirements"] --> B["Runtime lockfile"] --> C["Runtime environment"]
  B --> D["Test lockfile"] --> E["Test environment"]
  F["Test requirements"] --> D
Loading
High-Level Assessment

Updating both generated, hash-pinned lockfiles is consistent with the existing approach and keeps test dependencies aligned with runtime dependencies. Changing dependency declarations or application code is unnecessary for these version bumps.

Files changed (2) +698 / -683

Other (2) +698 / -683
requirements-test.txtAlign test lockfile with refreshed runtime pins +348/-341

Align test lockfile with refreshed runtime pins

• Applies the eight package version bumps and their new hashes to the test lockfile. Its dependency annotation also records Kubernetes as a consumer of oauthlib.

requirements-test.txt

requirements.txtBump eight hash-pinned runtime dependencies +350/-342

Bump eight hash-pinned runtime dependencies

• Updates boto3, botocore, confluent-kafka, grpcio, kubernetes, pydantic, pydantic-core, semver, and sqlalchemy pins and their hashes. The regenerated annotations also list Kubernetes as a consumer of oauthlib.

requirements.txt

@qodo-for-releng

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Qodo Logo

@lipoja
lipoja merged commit f999e0f into release-engineering:main Nov 20, 2026
22 of 23 checks passed
@lipoja
lipoja deleted the bump_requirements_2_main branch November 20, 2026 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants