Skip to content

🌱 chore: Bump Flower to 1.32.1 - #123

Open
chongshenng wants to merge 1 commit into
open-cluster-management-io:mainfrom
chongshenng:chore/bump-flwr-1.32.1
Open

🌱 chore: Bump Flower to 1.32.1#123
chongshenng wants to merge 1 commit into
open-cluster-management-io:mainfrom
chongshenng:chore/bump-flwr-1.32.1

Conversation

@chongshenng

@chongshenng chongshenng commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Summary

Flower 1.32.1 has been recently released. This PR bumps the versions for all flwr-related dependencies.

Related issue(s)

Fixes #

Summary by CodeRabbit

  • Chores
    • Updated the default Flower image tags from 1.26.1 to 1.32.1 across example apps and add-on tooling.
    • Updated Flower dependency constraints to require flwr>=1.32.1,<2 in the affected reference apps.
    • Refreshed Helm chart metadata and values to use 1.32.1 for the deployed components’ image tags.
  • Documentation
    • Updated the README build instructions to reference the newer Flower SuperExec base image tag (1.32.1).

@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9c8f8002-f49b-4937-aa1d-c859b4e1922f

📥 Commits

Reviewing files that changed from the base of the PR and between 91fcd65 and fddda04.

📒 Files selected for processing (8)
  • federated-learning-controller/README.md
  • federated-learning-controller/examples/flower/app-torch/Dockerfile
  • federated-learning-controller/examples/flower/app-torch/pyproject.toml
  • flower-addon/Makefile
  • flower-addon/charts/flower-addon/Chart.yaml
  • flower-addon/charts/flower-addon/values.yaml
  • flower-addon/cifar10/Containerfile
  • flower-addon/cifar10/pyproject.toml
✅ Files skipped from review due to trivial changes (4)
  • flower-addon/charts/flower-addon/Chart.yaml
  • flower-addon/charts/flower-addon/values.yaml
  • flower-addon/Makefile
  • federated-learning-controller/README.md
🚧 Files skipped from review as they are similar to previous changes (2)
  • federated-learning-controller/examples/flower/app-torch/pyproject.toml
  • flower-addon/cifar10/pyproject.toml

Walkthrough

This PR updates Flower 1.26.1 references to 1.32.1 in controller build instructions, app images, Helm chart metadata and values, and Python dependency constraints across federated-learning-controller and flower-addon.

Changes

Flower Version Bump

Layer / File(s) Summary
federated-learning-controller image and dependency updates
federated-learning-controller/README.md, federated-learning-controller/examples/flower/app-torch/Dockerfile, federated-learning-controller/examples/flower/app-torch/pyproject.toml
README build instructions, Dockerfile base image, and flwr dependency constraint are all bumped from 1.26.1 to 1.32.1.
flower-addon Makefile and Helm chart updates
flower-addon/Makefile, flower-addon/charts/flower-addon/Chart.yaml, flower-addon/charts/flower-addon/values.yaml
SUPERLINK_IMAGE/SUPERNODE_IMAGE tags, Helm chart appVersion, and image tags in values.yaml are bumped from 1.26.1 to 1.32.1.
flower-addon cifar10 image and dependency updates
flower-addon/cifar10/Containerfile, flower-addon/cifar10/pyproject.toml
Base image and flwr dependency constraint are bumped from 1.26.1 to 1.32.1.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description matches the template structure, but the Related issue(s) section is incomplete because it leaves "Fixes #" blank. Add the actual issue number or replace the placeholder with a valid reference, and keep the Summary aligned with the version bump.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title is concise and accurately summarizes the main change: bumping Flower to 1.32.1.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
flower-addon/cifar10/pyproject.toml (1)

11-11: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Consider pinning an upper bound alongside the floor constraint.

flwr>=1.32.1 is open-ended, so a future major/minor flwr release could be resolved by pip while the Containerfile and Makefile pin the superexec/superlink/supernode images to the exact 1.32.1 tag. Flower's own changelog notes that AppIo communication now enforces matching major.minor releases between components, so a client library newer than the pinned server images could break compatibility at runtime.

Consider constraining to the same minor series, e.g. flwr>=1.32.1,<1.33.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@flower-addon/cifar10/pyproject.toml` at line 11, The flwr dependency in
pyproject.toml is only lower-bounded, which can allow an incompatible newer
release to be installed against the pinned 1.32.1 container images. Update the
dependency spec in the pyproject.toml entry for flwr to keep the current floor
while adding an upper bound that stays within the same minor series, so the
client library remains compatible with the superexec/superlink/supernode images.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@flower-addon/cifar10/pyproject.toml`:
- Line 11: The flwr dependency in pyproject.toml is only lower-bounded, which
can allow an incompatible newer release to be installed against the pinned
1.32.1 container images. Update the dependency spec in the pyproject.toml entry
for flwr to keep the current floor while adding an upper bound that stays within
the same minor series, so the client library remains compatible with the
superexec/superlink/supernode images.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2b4ffa67-d7ed-44e8-b5b4-5fa5cbe2fb02

📥 Commits

Reviewing files that changed from the base of the PR and between f5844b9 and 91fcd65.

📒 Files selected for processing (8)
  • federated-learning-controller/README.md
  • federated-learning-controller/examples/flower/app-torch/Dockerfile
  • federated-learning-controller/examples/flower/app-torch/pyproject.toml
  • flower-addon/Makefile
  • flower-addon/charts/flower-addon/Chart.yaml
  • flower-addon/charts/flower-addon/values.yaml
  • flower-addon/cifar10/Containerfile
  • flower-addon/cifar10/pyproject.toml

@mikeshng mikeshng left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@chongshenng thank you for your contribution!

Could you please amend your commit with a sign-off? ie:

git commit -s --amend
git push -f ....

I will fix the e2e issue.

Signed-off-by: Chong Shen Ng <chong.shen@flower.ai>
@chongshenng
chongshenng force-pushed the chore/bump-flwr-1.32.1 branch from 91fcd65 to fddda04 Compare July 6, 2026 18:22
@chongshenng

Copy link
Copy Markdown
Contributor Author

Awesome, thanks @mikeshng. I've signed-off my commit as requested. Please let me know if any step is missing on my end.

@mikeshng mikeshng left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/approve

/lgtm

Thank you for this contribution!

@openshift-ci

openshift-ci Bot commented Jul 6, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chongshenng, mikeshng

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved label Jul 6, 2026

@mikeshng mikeshng left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@chongshenng I thought the unit test is just being flaky but after a few retries, it's still failing at the same spot. I am suspecting there were some lib/api changes from the flower version bump so this PR might need to make some code adjustments. Let me know if you think otherwise. Thanks!

@chongshenng

chongshenng commented Jul 6, 2026 via email

Copy link
Copy Markdown
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants