Skip to content

Bump Python requirements - #1434

Open
lipoja wants to merge 1 commit into
release-engineering:masterfrom
lipoja:bump_requirements_2_master
Open

lipoja wants to merge 1 commit into
release-engineering:masterfrom
lipoja:bump_requirements_2_master

Conversation

@lipoja

@lipoja lipoja commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Bump Python requirements

@qodo-for-releng

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

Copy link
Copy Markdown

PR Summary by Qodo

Refresh pinned runtime and test dependencies

⚙️ Configuration changes 🕐 40+ Minutes

Grey Divider

AI Description

• Refresh runtime dependency pins, including Celery, OpenTelemetry, Kubernetes, and SQLAlchemy.
• Align test dependencies with runtime pins, update pytest, and regenerate package hashes.
Merge Risk 🟡 Medium

Blast radius 🔴 High 💥 5 capabilities

  • 5 affected capabilities span independent functional scopes: IIB Kafka event publishing, IIB Kubernetes build orchestration, IIB background task processing, IIB object-storage integration, IIB observability integration.
  • The changed Celery dependency family is imported and initialized by the worker process and is used to dispatch and execute IIB background tasks.
  • This is one bounded task-processing integration; broker and worker package hops are implementation/deployment hops of the same end-to-end behavior.
  • The capability is the bounded S3 retrieval integration used by API request flows. boto3, botocore, the helper, and its callers form one end-to-end behavior rather than independent capabilities.
  • The producer configuration, serialization, queueing, polling, and delivery callback together implement one bounded event-publishing behavior.
  • They are not separate capabilities merely because initialization and delivery occur in different functions.
  • The Kubernetes client and its callers implement the bounded behavior of creating, querying, or managing build-related cluster resources.
  • Authentication dependencies are implementation hops within that integration, not separate capabilities.
  • The exporter, instrumentation packages, and their web/worker integration form one bounded observability capability.
  • HTTP, Celery, SQLAlchemy, and AWS instrumentation are consumers within that integration, not independent business capabilities.
Sources

requirements.txt[218-221]

celery==5.7.0 \
    --hash=sha256:18310a9c919f9029e4735367484d93e6a25cdfd30afdc474622cc263d9b35f6e \
    --hash=sha256:6a5dfcf6662287204f009a02002b9e66c83d4105e47ebabdc7079108772fc6f0
    # via iib (setup.py)

requirements.txt[948-951]

kubernetes==37.0.3 \
    --hash=sha256:862069ade8490916018a0a4e303050700f96f887edb5ec25db325a5212cb3923 \
    --hash=sha256:99a4d2154a884793e308e994a8808a64e548a17f2f525d52919eed1d9c2c58fe
    # via iib (setup.py)
Behavioral complexity 🟡 Medium 🧩 Compatibility cases

  • Before: the existing Kubernetes client and authentication dependency versions handled the repository's cluster API interactions.
  • After: the client and related dependency graph are replaced by newer versions.
  • New correctness condition: the client must preserve authentication, resource-model compatibility, request construction, and response handling across the supported cluster/API versions.
  • This is a compatibility condition introduced by the version transition, not a new application algorithm.
Sources

requirements.txt[948-951]

kubernetes==37.0.3 \
    --hash=sha256:862069ade8490916018a0a4e303050700f96f887edb5ec25db325a5212cb3923 \
    --hash=sha256:99a4d2154a884793e308e994a8808a64e548a17f2f525d52919eed1d9c2c58fe
    # via iib (setup.py)
Potential damage 🟡 Medium 🩹 Temporary loss

  • Affected requests can remain queued or fail to progress while workers cannot initialize or process tasks.
  • Reverting the dependency pins can restore code/runtime compatibility, but queued work may require broker/task replay or operator verification; the repository shows no persistent-state corruption or automatic repair mechanism.
  • Typically recoverable by restoring the previous dependency set and restarting workers, with possible manual inspection or replay of tasks that failed during the incompatible interval.
Sources

requirements.txt[218-221]

celery==5.7.0 \
    --hash=sha256:18310a9c919f9029e4735367484d93e6a25cdfd30afdc474622cc263d9b35f6e \
    --hash=sha256:6a5dfcf6662287204f009a02002b9e66c83d4105e47ebabdc7079108772fc6f0
    # via iib (setup.py)
Assessed commit b57a639
Diagram

graph TD
  Inputs["Dependency inputs"] --> Compile["pip-compile"] --> Runtime[("Runtime lockfile")] --> Test[("Test lockfile")] --> Tox["tox tests"]
  Runtime --> Install["Production install"]
Loading
High-Level Assessment

Keep the runtime and test lockfiles synchronized through pip-compile. This follows the project's existing hash-verified dependency workflow and is preferable to updating pins or hashes by hand.

Files changed (2) +4153 / -2008

Other (2) +4153 / -2008
requirements.txtRefresh hashed production dependency pins +2000/-942

Refresh hashed production dependency pins

• Bumps runtime and transitive packages, including Celery, boto3, Kubernetes, OpenTelemetry, Pydantic, and SQLAlchemy, with regenerated hashes. Removes the tzdata pin after it drops from the resolved dependency graph.

requirements.txt

requirements-test.txtSynchronize hashed test dependency pins +2153/-1066

Synchronize hashed test dependency pins

• Carries the refreshed runtime pins into the test environment and bumps pytest from 9.1.1 to 9.2.0. Regenerates hashes and removes the no-longer-resolved tzdata pin.

requirements-test.txt

@qodo-for-releng

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

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

MichalZelenak
MichalZelenak previously approved these changes Nov 20, 2026
Signed-off-by: Jan Lipovský <jlipovsk@redhat.com>
Assisted-by: Codex, Luna 6
@github-actions

Copy link
Copy Markdown

⚠️ Fullsend review agent did not run

The agent could not start because of a token mint failure.

View the workflow run

This branch has not been deployed

No deployments
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